feat(rules): implement Rule editing and copying

[andrewazores]

Welcome to Cryostat! 👋

Before contributing, make sure you have:

• Read the contributing guidelines
• Linked a relevant issue which this PR resolves
• Linked any other relevant issues, PR's, or documentation, if any
• Resolved all conflicts, if any
• Rebased your branch PR on top of the latest upstream main branch
• Attached at least one of the following labels to the PR: [chore, ci, docs, feat, fix, test]
• Signed all commits using a GPG signature

To recreate commits with GPG signature git fetch upstream && git rebase --force --gpg-sign upstream/main

---

Depends on cryostatio/cryostat#888
Related to #1581

Description of the change:

1. Adds router location state handling to the Rule creation form, similar to the Custom Recording Form. This allows navigation to the form with pre-filled form content based on the previous app context.
2. Adds a Rule table action button for Editing existing Rules. This opens the Rule creation form with identical content to the actioned Rule, locks the Rule name field (which is often used to uniquely identify rules) while allowing editing of all other fields, and fires a PATCH request to Cryostat to update the Rule on submission.
3. Adds a Rule table action button for Copying existing Rules. This opens the Rule creation form with identical content to the actioned Rule, but with _copy appended to the name, and will first a POST request to create a new rule on submission.

Motivation for the change:

Eases the user experience of managing Automated Rules. Currently the only way to create new Rules is to step through the form again and fill in everything, or else download the Rule as JSON and manually edit that and re-upload it. These two new actions allow users to use existing Rules (presets or their own definitions) as a base and adjust them as needed on the fly, or use them as a base for new and more refined Rules without needing to drop into manually editing JSON.

How to manually test:

1. Check out and build alongside feat(rules): allow patching of all rule fields cryostat#888
2. Go to Automated Rules
3. Click the action overflow menu on one of the preset Rules, or create/upload your own.
4. Click Edit. Verify that you are navigated to the Rule creation form, with the name field locked but all other fields editable. Make some changes, then click Update. Verify that you are navigated back to the Automated Rules view and the table content reflects your changes. If your Rule was previously enabled, verify that your edits are re-applied (ie recordings on matched targets are restarted with new settings).
5. Click the overflow menu and click Copy. Verify that you are navigated to the Rule creation form, with the name field having _copy appended. Make any other adjustments you'd like, then click the Create button to submit the form. Verify that you are navigated back to the Automated Rules view and the table content reflects your new Rule.
6. Repeat step 5 but remove _copy from the name. Try to submit the form and verify that an HTTP conflict notification appears and you are not navigated away. Change the rule name to a non-conflicting one and verify that creation now succeeds.
7. Download a Rule as JSON. Edit the JSON manually, giving it a new unique name and setting enabled: true. Re-upload the Rule and ensure that the table content reflects the new content, but with enabled overridden to false. Ensure manually toggling the Rule to enable it works as expected.

[github-actions]

This PR/issue depends on:

• feat(rules): allow patching of all rule fields cryostat#888
  By Dependent Issues (🤖). Happy coding!