fix: BucketRateLimitTable bug causing page crashes on Object Storage Bucket Create/Details drawer

[coliu-akamai]

Description 📝

• Quick fix to prevent the 'Oh snap' error from occurring due to no form context when on the Object Storage Create/Details drawer - this just restores the table's behavior to what it used to be on the Create/Details drawer

Target release date 🗓️

n/a

How to test 🧪

Reproduction steps

• with MSW and OBJ Gen2 flag enabled, navigate to Object Storage landing page
  • Create Bucket drawer: select a region with endpoints (Seattle) and click either endpoint E2 or E2
  • Bucket details drawer: click on the details button for a bucket with endpoint type E2 or E3
• oh snap'd

Verification steps

• Verify page no longer crashes when opening up bucket details drawer and bucket create drawer for steps above
• verify Bucket Properties page still works as expected
• yarn test BucketRateLimitTable.test.tsx

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
• 🧪 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

[coliu-akamai]

Old props for the radio - I'm unsure if the BucketRateLimitTable on the Details/Create drawer will eventually become part of a form, but for now placing this back in so that the page doesn't crash when trying to view the drawers

[github-actions]

Coverage Report: ✅
Base Coverage: 82.73%
Current Coverage: 82.73%

[pmakode-akamai]

Hi @coliu-akamai, Thanks for the fix 👍, but I believe this will be addressed in PR #10857. As planned, we have decided to remove the react-hook-form logic from the BucketRateLimitTable. You can refer to the PR description for more details.

Given that we already have the OBJ cleanup PR, I’m not sure if we still need this one 😬. What are your thoughts, @jaalah-akamai?

[coliu-akamai]

@pmakode-akamai thanks for pointing that out! Happy to close this PR then, since this one still has the react form logic.

[jaalah-akamai]

Thanks @coliu-akamai I'll include this PR in a future ticket since your work could be useful for whoever takes on this task later.