Fixes for score visibility in MMs and challenges

[vas3a]

This pull request updates the logic for handling submissions in the SubmissionService to better account for marathon match challenges and to improve data privacy for reviewers. The main changes focus on when to exclude certain submission properties based on challenge type and user role.

Logic improvements for marathon match challenges and reviewer privacy:

• Updated the condition to skip processing for challenges that either have a copilot or are marathon match challenges, ensuring marathon matches are handled consistently with other special cases.
• Removed unnecessary conditional checks before deleting sensitive properties (initialScore, finalScore, aiDecisionScore, aiDecisionStatus) from the submission object, ensuring these fields are always removed regardless of challenge type.