[23.1] Ignore errors with user-set job resources

[mvdbeek]

Fixes
https://sentry.galaxyproject.org/share/issue/735cef91223e42888ff9bc54ec93c2cb/, which is a problem that happens when a workflow with resource parameters is imported from another Galaxy instance, or when we change the available resource parameters and the selection becomes invalid.

Medium-term we need to stop doing this completely IMO and work with more abstract job requirements IMO, as this is a big barrier to transfer workflows from instance to instance and having them just work.

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.

[jmchilton]

I hate this - shouldn't we just make sure they aren't imported/exported? I thought we had code to do that - I get it might have bugs in it but it seems the right approach. Approving the PR though because I trust you.

[mvdbeek]

shouldn't we just make sure they aren't imported/exported?

of course we should also do that, but this wouldn't fix workflows users have already imported, or that the admins broke by changing the resource param definition. I'd be happy to do that, but I don't know if it is reasonable that downloading and re-uploading a workflow changes removes the resource parameter selection, that seems ... suboptimal as well ?