894 bug battlestart returns 500 when custom matchid is not a mongo objectid

[tickBit]

Brief description

There used to be allowed in the startBattle.dto.ts @IsString custom matchId, but using custom string caused 500 internal server error. To accept custom string without 500 internal server error requires changes to database schema.

Now matchId field must be MongoDB style string. It can be custom string with if it's also a 24 byte MongoDB string at the same time.

I git stashed the prettier/linting changes of other files.

Issue #894

Change list

• startBattle.dto.ts (require MongoID for matchId)
• added new test file for startBattle.dto.ts

[codecov-alt]

Codecov Report

✅ All modified and coverable lines are covered by tests.
see 4 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[CapoMK25]

Solid, approved. Be wary in the future with ObjectID vs string mismatches just in case, this PR/issue combo won't likely introduce them, but they're a common pain point in unit testing on bigger issues regardless.