Applicant and Opportunity collections API coverage

[zar92]

To support the Dev Recruit team, we should test the APIs for the Applicant and Opportunity collections.

The typical flow is a team lead will create an opportunity for a project. Then people will apply for the opportunity. When the role is filled, the opportunity will be unpublished, but not deleted so it can be reused in the future.

To test this,

1. We first need to make sure there is a project because an opportunity references a project.
2. Then we need to test create, get, list and update opportunity APIs.
3. Finally, we need to test create and get applicants.

Acceptance Criteria

Scenario: Testing Applications API coverage

• Given a project exists in the system
• When testing the following APIs:
  • Create an opportunity
  • Get an opportunity
  • List opportunities
  • Update an opportunity
  • Create an applicant
  • Get an applicant
• Then all API calls should return successful responses and follow the expected behavior

[dbradham]

@nikita-pardeshi-github do you have steps to test this in staging? If so, can you explain here how someone would test it in staging?

[dbradham]

https://github.com/dev-launchers/strapiv4/pull/211

Opportunity PR, linked above, has 100% coverage on the PR for this change.