feat(openapi-tooling): allow creating a react query layer on top of the generated client

[aramissennyeydd]

Hey, I just made a Pull Request!

What's better than 1 level of generated code? ⭐ 😎 ⭐

The goal of this PR is to demonstrate the viability of automatically generating react use hooks that can be used directly in code without having to instantiate the generated client. Most of that work is being done in plugins/catalog-react/src/generated/apis/DefaultApi.query.ts. Users should be able to immediately import the react query hook and get started writing UI components -- no need to worry about the API layer at all. Some parts of it leak out, as the request object has body, query, path keys, but I think that's fine for now. These hooks can be wrapped again if desired or overridden.

TODO:

• Update to use -common/client pattern from feat(openapi-tooling): stop inferring server types #23610 (this won't build until that's done)
• Add an example usage to catalog pages.

✔️ Checklist

• A changeset describing the change and affected packages. (more info)
• Added or updated documentation
• Tests for new functionality and regression tests for bug fixes
• Screenshots attached (for UI changes)
• All your commits have a Signed-off-by line in the message. (more info)

[backstage-goalie]

Missing Changesets

The following package(s) are changed by this PR but do not have a changeset:

• @backstage/catalog-client
• @backstage/repo-tools
• @backstage/plugin-catalog-backend
• @backstage/plugin-catalog-react

See CONTRIBUTING.md for more information about how to add changesets.

Changed Packages

Package Name	Package Path	Changeset Bump	Current Version
@backstage/catalog-client	packages/catalog-client	none	v1.6.5
@backstage/repo-tools	packages/repo-tools	none	v0.9.4-next.1
@backstage/plugin-catalog-backend	plugins/catalog-backend	none	v1.24.0-next.1
@backstage/plugin-catalog-react	plugins/catalog-react	none	v1.12.2-next.2

[github-actions]

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!

[github-actions]

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!

[aramissennyeydd]

Looks like some conflicts crept in, I'll take a look at those this week.

[Rugvip]

Oh I hadn't seen this, interesting! Is it ready for review?

[aramissennyeydd]

@Rugvip It's close, I'm trying to get some feedback internally around this. #23610 is ready for a re-review though :)

[github-actions]

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!