Implement cyberstorm disband team endpoint (TS-2313)

[Roffenlund]

Implement a DELETE endpoint for disbanding(deleting) teams in the Cyberstorm API.

Refs. TS-2313

[x753]

You can't disband a team with at least one package. You can't disband a team if you aren't the owner. These don't necessarily need to be expressed as API responses here (the current implementation adds "can_disband" to the context of the page and displays the blocking error at all times), but this information will need to be conveyed either here or in a retrieve API.

[Roffenlund]

You can't disband a team with at least one package. You can't disband a team if you aren't the owner. These don't necessarily need to be expressed as API responses here (the current implementation adds "can_disband" to the context of the page and displays the blocking error at all times), but this information will need to be conveyed either here or in a retrieve API.

I'm not sure if I understood you correctly, but not enforcing these checks at the API level could be risky since clients can bypass the UI. I believe the API should still validate and reject unauthorized disbanding attempts, regardless of how the UI handles it.

[x753]

You can't disband a team with at least one package. You can't disband a team if you aren't the owner. These don't necessarily need to be expressed as API responses here (the current implementation adds "can_disband" to the context of the page and displays the blocking error at all times), but this information will need to be conveyed either here or in a retrieve API.

I'm not sure if I understood you correctly, but not enforcing these checks at the API level could be risky since clients can bypass the UI. I believe the API should still validate and reject unauthorized disbanding attempts, regardless of how the UI handles it.

I meant they could use a unique response besides "You do not have permission to disband this team."