feat(ban): add endpoints for ban handling

[Antreesy]

☑️ Resolves

• Ref ⛔ Banning users and guests - Frontend #12293
• Provide a minimal frontend to test feature

Tip

To test handling a page navigation:

• create user with id banned
• create conversation with name ban user
• try to join as user

🖌️ UI Checklist

🖼️ Screenshots / Screencasts

Ban	-
List	-
	-
Page	-
	-

🏁 Checklist

• 🌏 Tested with Chrome, Firefox and Safari or should not be risky to browser differences
• 🖥️ Tested with Desktop client or should not be risky for it
• 🖌️ Design was reviewed, approved or inspired by the design team
• ⛑️ Tests are included or not possible
• 📗 User documentation in https://github.com/nextcloud/documentation/tree/master/user_manual/talk has been updated or is not required

[Antreesy]

We also forgot to add error handling for banned users/guests (but we can merge this first and do a follow-up for the other part):

• create user with id banned
• create conversation with name ban user
• try to join as user
• you should see 403 Error with response.data.ocs: {"data": { "error": "ban" }}
• probably we need to redirect to another page (like 404 - Not Found, but specific for 403 / bans)

[nickvergessen]

Should be two requests to the server, or could be done with a single entrypoint?

I think I would add the options to the existing endpoint.

[marcoambrosini]

Sorry for late reply, looks good to me :)
Maybe we could repeat the name instead of referring to "participant" in the checkbox text

[DorraJaouad]

Tested 🦅