PM-5925 gitea challenge teams

[vas3a]

Related JIRA Ticket:

https://topcoder.atlassian.net/browse/PM-5925

What's in this PR?

This pull request introduces support for configuring Gitea team synchronization in the challenge editor. It adds the ability to search, select, and persist Gitea teams as part of challenge metadata, along with robust validation and utility functions to ensure data integrity. The changes are well-covered by new unit tests.

Gitea Team Support in Challenge Editor

Constants and Model Definitions:

• Added GITEA_METADATA_FIELD constant and related search configuration options for Gitea teams in constants.ts and challenge-editor.constants.ts. [1] [2]
• Introduced the GiteaTeam model to represent Gitea teams, and exported it for use throughout the codebase. [1] [2]

Challenge Editor Form and Validation:

• Updated ChallengeEditorFormData to include a giteaTeams field, and extended the challenge editor schema to validate uniqueness and presence of required fields for selected Gitea teams. [1] [2]
• Added comprehensive tests for Gitea team validation in the challenge editor schema.

Gitea Team Search Service:

• Implemented the searchGiteaTeams service for searching Gitea teams via the API, including normalization and error handling. Exported the service for use. [1] [2]
• Added unit tests for the Gitea team search service, covering normalization, error handling, and edge cases.

Challenge Metadata Mapping Utilities:

• Enhanced challenge editor utilities to map Gitea teams to and from challenge metadata, ensuring only unique teams are stored and loaded. Added thorough tests for these utilities. [1] [2] [3] [4] [5]

These changes collectively enable challenges to be linked with Gitea teams, supporting participant synchronization and improving integration with Gitea-based workflows.