feat: export/publish built-in managed gateway apis

[David Schneiderbauer (daviian)]

resolves #501

[David Schneiderbauer (daviian)]

@microsoft-github-policy-service agree company="Cloudflight"

[Wael Kdouh (waelkdouh)]

Hi we just released v6 release candidate. Can you please try to apply your PR on the new code base?

[Wael Kdouh (waelkdouh)]

David Schneiderbauer (@daviian) will you be able to resubmit the PR against the new v6 code base?

[David Schneiderbauer (daviian)]

Wael Kdouh (@waelkdouh) I'll try to find some time this week to check out the new code base and apply my changes.

[David Schneiderbauer (daviian)]

Wael Kdouh (@waelkdouh) I need some clarification about this line https://github.com/Azure/apiops/blob/main/tools/code/publisher/App.cs#L51.
Isn't the order important when importing changed files? As in, you cannot assign a gateway to an API that has not yet been created before.
How is this ensured in v6?

I think I've found the answer.
Please let me know if the solution is fine or needs changes.

[David Schneiderbauer (daviian)]

I've updated the PR so that the conflicts from recent merges have been resolved.
guythetechie can you have a look at the PR please?

[David Schneiderbauer (daviian)]

Is there any chance this can be removed soonish?

[Anna Teier (glenroy37)]

Is there any timeframe when this will be reviewed and merged? We currently have to build the apiops publisher manually with the changes from this PR and it seems to be abandoned for nearly a year now

[Wael Kdouh (waelkdouh)]

Anna Teier (@glenroy37) Let me take a look and get back to you.