Warn, don't fail, when an API is not found when publishing an API product

[jeroenmaes]

Scenario:

• ApiOps is used in a MultiRepo setup (~multiple independant teams)
• API Products are managed & published in the central team repo
• APIs are managed by the teams

When an API product is published to a higher environment, where the API itself does not exists yet, the deployment of the API Product fails the publish process.

PR Changes: Catch the "API Not Found" exception when publishing an API Product and log a warning instead of throwing an exception.

[jeroenmaes]

@jeroenmaes please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

• (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

• (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

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

Contributor License Agreement

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

[waelkdouh]

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

[waelkdouh]

This has been addressed in v6. Please try again in v6 and if the issue still persists please open a new PR. Thanks for your contributions.