Account for shared usage between TS and galaxy apps

[jdavcs]

This is rather unfortunate, but for now I don't see any other way around this other than removing typing of method params. The model may belong to galaxy or tool shed (both User and APIKeys), and the only way of adding this would be to import from tool shed. (ref 09c2efc#r128430531)

If we have to share this code with tool shed, I think it belongs in a separate utility library shared across both galaxy and tool shed, not in galaxy's managers.

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]

The tool shed branch has some small typing tweaks to get us toward some protocols that are shared but I agree the current situation around shared code is problematic. The typing is just foregrounding errors we've always had. Certainly the manage taking a Base app that is shared with the tool shed and not the Galaxy app is... a step forward from just using an untyped trans.app everywhere.

Thanks for the fix.

[jmchilton]

Thanks so much!