Refactor of User-Reported Dataset Error Emails

[hujambo-dunia]

• This is PR "Part 1 of 2" to address the [feature request] There seems to be no way to report a 'tool error' if that tool is apply rules #17560 issue.
• This PR (mostly front-end changes) handles much needed: (1) decoupling of View vs. Controller and (2) object-oriented abstraction.
• The PR "Part 2 of 2" (mostly back-end changes) handles API abstraction to allow for user-submitted error reporting on other Objects (eg. 'Tools').

How to test the changes?

(Select all options that apply)

• I've included appropriate automated tests.
• This is a refactoring of components with existing test coverage.
• Instructions for manual testing are as follows:
  1. [add testing steps and prerequisites here if you didn't write automated tests covering all your changes]

License

• I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

[jdavcs]

Can you, please, reword the commit description as per our guidelines (https://github.com/galaxyproject/galaxy/blob/dev/CONTRIBUTING.md#how-to-contribute, item 6) - i.e., short imperative sentence, then space, followed by detailed description when needed). It really matters for working with git history and for release notes.

[ahmedhamidawan]

Hey @hujambo-dunia ! Could you please rebase to resolve these conflicts?

Additionally, seems like you've created a UserReportingError component, whereas, I had added an EmailReportForm component recently which seems to do the same thing. So maybe those will have to be consolidated.

Update: If I locally refactor this, I reckon it'd make sense to restrict this to the backend change with the API abstraction, because the EmailReportForm seems to handle the client changes here the exact same way.

[guerler]

Bumping this to 26.1 for now. Happy to bring it back to 26.0 if it is still intended for that release and can be made merge ready.