feat: Model Competitions - Competition Model Services

[roselynh100]

Changelogs

• Turned CompetitionSpecification into an abstract class, which throws an error if instantiated → must use PredictionBasedCompetition or ModelBasedCompetition instead
  • These implement submit_entry differently (also, users can call competition.submit_predictions instead)
  • Replaced all CompetitionSpecification instances with PredictionBasedCompetition (mostly in tests)
• New function submit_competition_model allows users to submit a model to a competition
  • A model artifact id must be passed in, and this gets submitted to the competition
• Updated submit_to_competition.ipynb tutorial with instructions for submitting to a model-based competition

---

Checklist:

• Was this PR discussed in an issue? It is recommended to first discuss a new feature into a GitHub issue before opening a PR.
• Add tests to cover the fixed bug(s) or the newly introduced feature(s) (if appropriate).
• Update the API documentation if a new function is added, or an existing one is deleted.
• Write concise and explanatory changelogs above.
• If possible, assign one of the following labels to the PR: feature, fix, chore, documentation or test (or ask a maintainer to do it for you).

---

discussion related to that PR

[roselynh100]

This is the only new change in CompetitionSpecification !

[Andrewq11]

Excellent work, @roselynh100! I've left a few small comments but overall, it is very well done 🚀

Let me know if you have any questions about them.

[Andrewq11]

Nice call on instantiating this here instead of just pulling the returned artifact ID from the json. Either would work, but this feels safer with the Pydantic.