Migrate cloud API to Fast API

[heisner-tillman]

This is a part of #10889.

Summary

• Add pydantic models
• Operations now return pydanctic models
• Removed the mapping to the legacy route and add FastAPI routes

How to test the changes?

• I've included appropriate automated tests.
• This is a refactoring of components with existing test coverage.
• Instructions for manual testing are as follows:
  You can find the interactive API documentation here: http://127.0.0.1:8080/api/docs#/cloud

License

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

[heisner-tillman]

I have not written any tests for this yet as I do not have cloud-based storage.
I would appreciate it if someone could help me with this.
I also suspect that there are still bugs, but it is hard to find or fix them without tests.

[mvdbeek]

Are you planning to do more routes ? I think it'd be good to coordinate a little, this route for instance we should probably deprecate.

[bgruening]

@mvdbeek we are planning to migrate a few more routes yes. Can we use the meta issue to track which ones are needed and which not?

[heisner-tillman]

@mvdbeek I was planning to try my hand at the old users routes next.

[mvdbeek]

That seems like a good idea for these routes:

There are more specific routes for various small things like these:

the ones that end with /inputs are anlittle weird and tied to the shape of the form we use for the UI. You can port them if you really want, but those should probably be refactored or dropped soon-ish.

[davelopez]

Nice first try! 👍

I guess the important part here is to have the routes marked as deprecated in the interactive docs, but we should try to keep the same response models while they are still part of the API.