[24.2] Allow access to published workflows

[mvdbeek]

Which is how it was before
2ff6aa5. Alternatively I could update all iwc workflows to also be accessible. I guess that would be more cosistent ...

The UI forces you to make the workflow accessible if you want to publish the workflow, which makes sense I guess.

(Please replace this header with a description of your pull request. Please include BOTH what you did and why you made the changes. The "why" may simply be citing a relevant Galaxy issue.)
(If fixing a bug, please add any relevant error or traceback)
(For UI components, it is recommended to include screenshots or screencasts)

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.

[mvdbeek]

I have fixed up all of the iwc workflows. I guess it's unlikely that many people publish by API, so maybe the more solid thing to do is to make the PUT logic also toggle the importable flag (if not explicitly receiving a contradictory argument).