SCRUM-61 implement conduct debate button

[Peres270]

SCRUM-61 – Implement conduct debate button

Implemented the "Conduct Debate" button on the debate details page.

What was done
Added a new debate details page (/debates/[debate_id])
Created MarshalPanel component to display marshal actions
Integrated data fetching:
/auth/me to get current user
/tournaments/{id}/debates/{debate_id} to fetch debate details
/users/{id}/tournaments/{id}/roles to determine user roles
Implemented conditional rendering:
Button is only visible for users with Marshal or Organizer roles
Added external link to DebateCore with encoded motion

Notes / Limitations
Could not fully validate the feature end-to-end because the backend currently returns no debates (GET /tournaments/{id}/debates returns an empty array)
As a result, it was not possible to access a real debate details page to visually confirm the button rendering

The implementation is complete from the frontend side and should work correctly once a valid debate is available in the backend.

[Mateusz-Dobrzynski]

I can confirm, the /tournaments/{tournament_id}/debates/{debate_id} endpoint returns 500; I'm creating a task for it. However, you do not need this endpoint to complete the task. You only need to use /users/{user_id}/tournaments/{tournament_id}/roles to check user roles and this endpoint works just fine (refer to the testing section).

There are some problems with this PR.

1. The component does not look the way it should:

Original design

Current implementation

2. Problems with the code need to be resolved.

• Pass motion to the component and remove other props.
• Write unit tests for the component:
  • Mock /users/{user_id}/tournaments/{tournament_id}/roles and check if the component is rendered/not rendered depending on whether the user is a Marshal or not.
  • Ensure the button contains a valid link when you pass a motion to it.
• Change component styling to match the design.

[Mateusz-Dobrzynski]

Again: do not translate Polish strings; it will be done later by a native speaker.

[Mateusz-Dobrzynski]

You could have skipped creating this file, though I understand it might have been created due to a misunderstanding about the scope of the task that we had.

[Mateusz-Dobrzynski]

Why did you create this variable in the outer scope? It can be defined inside the component.

[Mateusz-Dobrzynski]

Why did you make the props generic so that all logic must be handled outside of the component? Instead, you can only pass motion and generate the href here. Displayed strings can be handled as static translations, as they will not change. Refer to the design.