Frontend: Allows users to update secrets

Why are we doing this work

This issue is for integrating the update mutation from #470397 (closed) and letting users (with the correct permissions) update secrets from the Secrets Manager.

Note: This will not include listing the entities affected by the change. This will be implemented in #543162.

Relevant links

• Closed Experiment/Beta Secrets Manager Placement Design SSOT - Figma link
• Backend API issue: Update secret (Backend) (#470397 - closed)

Non-functional requirements

• Documentation
• Feature flag: secrets_manager and ci_tanukey_ui
• Testing

Implementation plan

The edit form is mostly the same as the create form, so we can reuse the existing frontend component for this. We also need to fetch the existing secrets data, and account for design changes between the Create and Edit form. For example, the user cannot edit the name, and there is an additional button that enables editing the value (which we do not fetch).

We should also check that the links to the Edit form have been updated to use the breadcrumbs. There are two links: one from the secret detail page, and one from the index page (secrets table).

Verification steps

1. Set up openbao on your gdk.
2. Enable the Secrets Manager on gdk.
3. Go to your project settings (Secure > Secrets manager) and create a secret.
4. From the secret details page and the secrets table, users should be able to access the edit form.