Add config option in metastore settings to stop forcing redirect

[zedmonds96]

Fixes #4326

Describe your changes

Added a configuration option in metastore settings. If checked, the user will be redirected to the datasets view when creating/editing a dataset. If unchecked, the user will remain on the node page for the dataset instead of the redirect.

• Added configuration key redirect_to_dataset to metastore.settings.yml.
• Added configuration schema for redirect_to_dataset to metastore.schema.yml.
• Added redirect_to_datasets checkbox to the metastore settings form in DkanDataSettingsForm.php
• Restructured the metastore settings form for future maintainability.
• Modified metastore_admin_form_submit() in metastore_admin.module to get the checkbox value on submission to determine redirect behavior.
• Added update hook metastore_update_8010() to metastore.install to set the default value of the config.
• Created functional tests for when the configuration is enabled and disabled in RedirectToDatasetsTest.php

QA Steps

• Navigate to DKAN -> Metastore Settings.
• Confirm that the "Redirect to datasets view after form submit" checkbox exists.
• Verify that it is checked by default.
• Go to Content -> Add Content -> Create Dataset.
• Fill in the required fields and submit the form.
• Expected result: You should be redirected to the datasets view after submission.
• Return to Metastore Settings.
• Verify the checkbox is still checked, then uncheck it and save.
• Edit the dataset you just created, make a small change, and submit again.
• Expected result: You should stay on the dataset’s node page after submission instead of being redirected.

Checklist before requesting review

If any of these are left unchecked, please provide an explanation

• I have updated or added tests to cover my code
• [N/A] I have updated or added documentation

[zedmonds96]

Need to add a test for this, moving back to draft.

[zedmonds96]

There is a code climate issue with the metastore settings form having more than 25 lines. It has 29. In my opinion it is readable and well structured, so we should allow it as-is.

Updated the form structure to satisfy codeclimate now and in the future.

[dafeder]

Looks good @zedmonds96 - see one request about the test approach and another about form text