Removes Sql Schema Versions (7,8,9,10)

[mahajan-xor]

Description

This PR removes older sql schema versions (7.sql,58.sql,9.sql,10.sql).

Also removed below class files under Features.Storage.TvpRowGeneration folder to solve build error issues
1.CompartmentAssignmentV1RowGenerator 2.DateTimeSearchParameterV1RowGenerator 3.NumberSearchParameterV1RowGenerator 4.QuantitySearchParameterV1RowGenerator 5.ReferenceSearchParameterV2RowGenerator 6.ReferenceTokenCompositeSearchParameterV2RowGenerator 7.ResourceWriteClaimV1RowGenerator 8.StringSearchParameterV1RowGenerator 9.TokenDateTimeCompositeSearchParameterV1RowGenerator 10.TokenNumberNumberCompositeSearchParameterV1RowGenerator 11.TokenQuantityCompositeSearchParameterV1RowGenerator 12.TokenSearchParameterV1RowGenerator 13.TokenStringCompositeSearchParameterV1RowGenerator 14.TokenTextSearchParameterV1RowGenerator 15.TokenTokenCompositeSearchParameterV1RowGenerator 16.UriSearchParameterV1RowGenerator

Addresses [user story #].
User Story 104513: Remove old schema versions from FHIR solution

Testing

Describe how this change was tested.

FHIR Team Checklist

• Update the title of the PR to be succinct and less than 65 characters
• Add a milestone to the PR for the sprint that it is merged (i.e. add S47)
• Tag the PR with the type of update: Bug, Build, Dependencies, Enhancement, New-Feature or Documentation
• Tag the PR with Open source, Azure API for FHIR (CosmosDB or common code) or Azure Healthcare APIs (SQL or common code) to specify where this change is intended to be released.
• Tag the PR with Schema Version backward compatible or Schema Version backward incompatible or Schema Version unchanged if this adds or updates Sql script which is/is not backward compatible with the code.
• CI is green before merge
• Review squash-merge requirements

Semver Change (docs)

Patch|Skip|Feature|Breaking (reason)

[SergeyGaluzo]

🕐

[SergeyGaluzo]

Please remove all versions up to 60. Versions can be still present in SchemaVersion.cs.

[mahajan-xor]

Please remove all versions up to 60. Versions can be still present in SchemaVersion.cs.

Yes @SergeyGaluzo I will remove all versions up to 60 . But I'm doing it in chunks because it is getting lot of issues when I try to delete all files at once. So I'm deleting 5 to 10 versions at time and solving build issues after that raising PR for same. Same approach I have discussed and finalized with Brendan and Robert.

revoking review