test: [M3-8616] - Fix failures in DBaaS update tests

[jdamore-linode]

Description 📝

Recent improvements made for DBaaS v2 began causing intermittent test failures in update-database.spec.ts. This PR makes a few changes to resolve these failures:

• Mocks the dbaasV2 feature flag to be disabled
• Mocks the account so that it is lacking the Managed Databases Beta capability
• Updates the test's database mock to force the platform field to always reflect the legacy platform
  • ℹ️ This seems to be what actually fixed the test, and appears to take precedence over the DBaaS v2 feature flag and account capability
  • ⛔️ Going forward we might want to discourage using pickRandom or any similar utils that make our factories less deterministic since they're used throughout the codebase/tests

Target release date 🗓️

N/A

How to test 🧪

We can't rely solely on CI for this since this failure is only intermittent, but running the tests in update-database.spec.ts a few times in a row without observing any failures can help increase confidence that the tests are fixed.

repeat 3 yarn cy:run -s "cypress/e2e/core/databases/update-database.spec.ts"

As an Author I have considered 🤔

Check all that apply

• 👀 Doing a self review
• ❔ Our contribution guidelines
• 🤏 Splitting feature into small PRs
• ➕ Adding a changeset
  • Thinking a changeset might not be necessary here since these failures didn't make it to a release -- any thoughts?
• 🧪 Providing/Improving test coverage
• 🔐 Removing all sensitive information from the code and PR description
• 🚩 Using a feature flag to protect the release
• 👣 Providing comprehensive reproduction steps
• 📑 Providing or updating our documentation
• 🕛 Scheduling a pair reviewing session
• 📱 Providing mobile support
• ♿ Providing accessibility support

[github-actions]

Coverage Report: ✅
Base Coverage: 87.12%
Current Coverage: 87.12%

[mjac0bs]

Going forward we might want to discourage using pickRandom or any similar utils that make our factories less deterministic since they're used throughout the codebase/tests

@jdamore-linode - Should we call this out in our docs?

Thanks for the quick investigation and fixes - I did observe this passing 5/5 times locally.

[jdamore-linode]

Should we call this out in our docs?

@mjac0bs Good idea! I just pushed a pretty quick note to that section, but there might be some opportunity to flesh out our factory guidelines a bit in the future

[jdamore-linode]

Merging despite test failures:

• DBaaS update tests are passing, which was the goal of this PR
• Failures (including unit test failures) are confirmed not to be related to these changes