Added support for dropped databases on Managed Instance

[v-djnisi]

Latest improvements:

Adding dropped database, as well as short term retention for dropped databases to readme.me. API for both of these is in prod for quite some time.

Contribution checklist:

• I have reviewed the documentation for the workflow.
• Validation tools were run on swagger spec(s) and have all been fixed in this PR.
• The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

• Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
• adding/removing APIs.
• adding/removing properties.
• adding/removing API-version.
• adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

• If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
  Please follow the link to find more details on API review process.

[openapi-portal-comment]

If you're a MSFT employee, click this link
to view this PR's validation status on our new OpenAPI Hub spec management tool.

[azuresdkci]

Hello!!

The Rest API Specs team wishes everyone a happy holiday and would like to kindly inform you that responses and review to Pull request will be delayed during the holiday period (now -> 2nds of January) to allow for Awesome reviewers to have an awesome time with their families during the holidays!

Thanks and Have a WONDERFUL HOLIDAY

[AutorestCI]

Automation for azure-sdk-for-ruby

A PR has been created for you based on this PR content.

Once this PR will be merged, content will be added to your service PR:
Azure/azure-sdk-for-ruby#2143

[AutorestCI]

Automation for azure-sdk-for-python

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-python#3769

[AutorestCI]

Automation for azure-sdk-for-js

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-js#570

[AutorestCI]

Automation for azure-sdk-for-go

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-go#3910

[azuresdkci]

Can one of the admins verify this patch?

[AutorestCI]

Automation for azure-sdk-for-java

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-java#2138

[AutorestCI]

Automation for azure-sdk-for-node

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-node#4181

[v-djnisi]

Here are scenario tests: https://github.com/Azure/azure-sdk-for-net/pull/5107

[jhendrixMSFT]

This change introduces a new ARM violation, see the task result here. This either needs to be fixed or ARM team to provide an approval for suppression.

[KrisBash]

@v-djnisi The arm validation error concerns the lack of a PATCH api on the restorableDroppedDatabases. A PATCH API is required on all tracked resources, which is why this resource has been flagged. Note, the linting runs on all files in the commit, not just the changed files - which is why this is being flagged on an existing file. I notice that there is no PUT api for this resource type. Can the user not create/update this resource? If that is the case, I think it would make sense to request a suppression for this validation error. Is this something you can comment on?

[v-djnisi]

Correct, this resource can't be created or updated. Once database is dropped it transitions to dropped databases, and it's only purpose is to provide data and backups so that we can restore it afterwards if necessary.

[KrisBash]

Signing off from ARM. For this specific case, a suppression should be requested given the nature of the resource

[v-djnisi]

Anything required from me, regarding the suppression?

[jhendrixMSFT]

@v-djnisi yes please send an email to armpm and adxsr with a request for the suppression along with an explanation.

[v-djnisi]

Added suppression.