NetApp RP minor update and validation fixes

[leonardbf]

Removed obsolete Mount Target Delete operation.
Fixed autorest pagination warnings.
(NetApp ticket NFSAAS-1505)

[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.

[AutorestCI]

Automation for azure-sdk-for-go

Nothing to generate for azure-sdk-for-go

[AutorestCI]

Automation for azure-sdk-for-js

Nothing to generate for azure-sdk-for-js

[AutorestCI]

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

[AutorestCI]

Automation for azure-sdk-for-node

Nothing to generate for azure-sdk-for-node

[AutorestCI]

Automation for azure-sdk-for-python

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

[AutorestCI]

Automation for azure-sdk-for-java

Nothing to generate for azure-sdk-for-java

[azuresdkci]

Can one of the admins verify this patch?

[hovsepm]

Couple of warnings - removing an operation and marking return values as paginated will be a breaking change in strongly typed languages however since the swagger is in preview folder we do not block merge. Please confirm that it is ok for you to break customers code.

[leonardbf]

Couple of warnings - removing an operation and marking return values as paginated will be a breaking change in strongly typed languages however since the swagger is in preview folder we do not block merge. Please confirm that it is ok for you to break customers code.

Yes, the removal of the operation is ok and is because it is no longer present in the application.
The pagination (forcing null) was added because without this block the autorest validation was producing warnings, e.g. Based on the response model schema, operation 'Operations_List' might be pageable. Consider adding the x-ms-pageable extension