feat: expansion of gitea api to handle columns

[eyad-hussein]

Resolves #31769

Implementation details:

• Create a columnAssignment middleware similar to the middlewares already implemented(eg orgAssignment) to extract the ContextUser. After that, the other middlewares will check if the doer has the necessary permissions to execute the request.
• Create necessary handlers for each endpoint

Projects:

• PATCH /projects/{project_id}/{action:close|open}
• PUT /repos/{owner}/{repo}/projects/{type:issues|pulls}

Columns:

• GET /projects/columns/{column_id}
• PATCH /projects/columns/{column_id}
• DELETE /projects/columns/{column_id}
• GET /projects/{project_id}/columns
• POST /projects/{project_id}/columns
• PATCH /projects/{project_id}/columns/move
• PATCH /projects/{project_id}/columns/{column_id}/move
• PUT /projects/columns/{column_id}/default

Tests

• Tests

Other endpoints for projects are implemented but i can remove them from the pr if requested.

[GamerGirlandCo]

one thing to note is that these endpoints appear to only work with the access_token query param, which has been marked as deprecated in favour of authorization headers. other than that, awesome work! hope to see this merged in a timely fashion :D

[techknowlogick]

@eyad-hussein thanks for this PR! Even though tests aren't yet included, is it okay if a review is started for the rest of the code?

[eyad-hussein]

@techknowlogick Sure, feel free to start reviewing the code.