feat(project): add new endpoint

[agong-coveo]

Added this new endpoint

• This endpoint gets the associated project ID(s) per provided resource ID(s);
• Takes the org ID, the resource type of the provided resourced ID(s) as params, and the resource IDs in the body.

Acceptance Criteria

• My changes are publicly available, documented, and deployed in production. (i.e. on Swagger)
• JSDoc annotates each property added in the exported interfaces
• The proposed changes are covered by unit tests
• Commits containing breaking changes a properly identified as such
• README.md is adjusted to reflect the proposed changes (if relevant)
• My merge commit message will be conventional (See Conventional Commit)

[FelixBlaisThon]

If I understand, lets say Org A has few projects, if I have an ART model and I send my orgID and Model as a resource type (with ART model in the body), the call will return me all the projects that match that ?

[agong-coveo]

If I understand, lets say Org A has few projects, if I have an ART model and I send my orgID and Model as a resource type (with ART model in the body), the call will return me all the projects that match that ?

Correct 👍 If you provide the orgId, ML_MODEL as the resource type and pass the ART model's ID in the body, it will return you a response containing the project IDs that are associated to it. The format will look like so:

[
  {
    "id": "provided-art-model-id",
    "projectIds": [
      "random-associated-project-to-art-model-id"
    ]
  }
]

[github-actions]

🎉 This PR is included in version 54.7.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀