fix: fix url for flask build

[DDDDDanica]

Explanation

This MR fix the url for downloading flask artifacts.

You can try build(flask) in the downstairs comment area:
#17784 (comment)

Screenshots/Screencaps

Before

After

Manual Testing Steps

Pre-merge author checklist

• I've clearly explained:
  • What problem this PR is solving
  • How this problem was solved
  • How reviewers can test my changes
• Sufficient automated test coverage has been added

Pre-merge reviewer checklist

• Manual testing (e.g. pull and build branch, run in browser, test code being changed)
• PR is linked to the appropriate GitHub issue
• IF this PR fixes a bug in the release milestone, add this PR to the release milestone

If further QA is required (e.g. new feature, complex testing steps, large refactor), add the Extension QA Board label.

In this case, a QA Engineer approval will be be required.

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[metamaskbot]

Builds ready [b86eeb3]

• builds: chrome, firefox
• builds (beta): chrome, firefox
• builds (flask): chrome, firefox
• build viz: Build System
• mv3: Background Module Init Stats
• mv3: UI Init Stats
• mv3: Module Load Stats
• mv3: Bundle Size Stats
• mv2: E2e Actions Stats
• code coverage: Report
• storybook: Storybook
• typescript migration: Dashboard
• all artifacts
• bundle viz:

  • background: 0, 1, 2, 3, 4
  • common: 0, 1, 2, 3, 4, 5
  • content-script: 0
  • contentscript: contentscript
  • disable-console: disable-console
  • inpage: inpage
  • policy-load: policy-load
  • sentry-install: sentry-install
  • ui: 0, 1, 10, 11, 2, 3, 4, 5, 6, 7, 8, 9

Page Load Metrics (1663 ± 40 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	104	148	124	14	7
		domContentLoaded	1450	1784	1632	95	46
		load	1450	1784	1663	82	40
		domInteractive	1450	1784	1632	95	46

Bundle size diffs

• background: 0 bytes
• ui: 0 bytes
• common: 0 bytes

[Gudahtt]

LGTM! Though it seems that the beta builds have the exact same problem. That can be fixed just a couple of lines up from here

[DDDDDanica]

@Gudahtt thanks for reviewing, the beta build will be covered here as part of automation task ~ it will differ from flask one actually when we generate flask for beta commits, the solution is a bit more complex ~

[Gudahtt]

I just mean the beta builds linked in the metamaskbot comment. Similar to Flask, these are just preview builds for people working on PRs that only affect beta/Flask/etc. These simple preview builds might still be useful for beta, independently of the work to trigger the "real" builds only when we want a real build. Not a big deal though.