fix: fix invalid gamemode id again for hero stats

[TeKrop]

Blizzard changed the id again for Competitive data. As they're not returning any error when the input is invalid, it hasn't been detected. I changed the id again so it works fine.

Summary by Sourcery

Bug Fixes:

• Correct the Competitive gamemode ID mapping in hero stats summary parsing so Competitive data is retrieved properly.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the competitive gamemode ID mapping for hero stats parsing to use the newly correct Blizzard value so competitive hero stats resolve correctly again.

File-Level Changes

Change	Details	Files
Update competitive gamemode identifier used when parsing hero stats so it matches Blizzard’s latest ID.	Change the PlayerGamemode.COMPETITIVE mapping value in GAMEMODE_MAPPING from "2" to "1" so competitive mode hero stats are requested/parsing with the correct gamemode ID.	app/domain/parsers/hero_stats_summary.py

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#395	Ensure that the /heroes/stats endpoint correctly respects the gamemode query parameter so that competitive and quickplay return distinct stats by using the correct internal gamemode IDs.	✅

Possibly linked issues

• #Map filter with competitive gamemode returns 400 for all maps: Issue’s competitive+map 400s stem from wrong competitive gamemode ID; PR fixes that ID mapping.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud