[BodyTopLevelProperties] Add "managedByExtended" to allowed list of top-level properties

[Copilot]

Summary

Added managedByExtended to the list of allowed body top-level properties for ARM resources in compliance with ARM guidelines.

Changes Made

Code Changes

• ✅ Updated allowedBodyTopLevelProperties array in arm-resource-validation.ts to include managedbyextended
• ✅ Updated propertiesBagTracked array in arm-resource-validation.ts to include managedbyextended
• ✅ Updated error message to list all allowed properties: name, type, id, location, properties, tags, plan, sku, etag, managedBy, managedByExtended, identity, kind, zones, systemData, extendedLocation

Documentation Changes

• ✅ Updated body-top-level-properties.md to include managedByExtended and all properties
• ✅ Updated rules.md to include managedByExtended and all properties
• ✅ Fixed casing inconsistencies (extendedLocation)

Testing

• ✅ Updated existing test file body-top-level-properties-real-swagger.json to include managedByExtended property
• ✅ Removed separate test file to consolidate test cases
• ✅ All tests pass successfully (438 spectral tests + 90 native tests)
• ✅ Build and lint checks pass

Package Management

• ✅ Bumped package version to 2.2.2 in package.json
• ✅ Updated CHANGELOG.md with version 2.2.2 entry for this change

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[raosuhas]

@copilot instead of creating a new json file for the test , can you just update one of the existing files to include these tests ?

[Copilot]

Updated! I've added the managedByExtended property to the existing body-top-level-properties-real-swagger.json file instead of creating a new test file. The separate test file has been removed and the test case now uses the updated existing file. All tests pass. (commit 90d4543)

[mikeharder]

@copilot: update the package.json and changelog associated with this package

[Copilot]

@copilot: update the package.json and changelog associated with this package

Added Rush change file for version tracking. The change file will automatically bump the patch version and update the changelog when the next release is published. (commit cab0d67)

[mikeharder]

@copilot: update the package.json and changelog associated with this package

Added Rush change file for version tracking. The change file will automatically bump the patch version and update the changelog when the next release is published. (commit cab0d67)

@copilot: Actually, we directly update package.json and readme.md now, instead of using rush. See PR #783 as an example. For this PR, bump the patch version by one.

[mikeharder]

@copilot: update the package.json and changelog associated with this package

Added Rush change file for version tracking. The change file will automatically bump the patch version and update the changelog when the next release is published. (commit cab0d67)

@copilot: Why did you think you needed to use Rush to update this? Was it some documentation in the repo?

[Copilot]

@copilot: update the package.json and changelog associated with this package

Added Rush change file for version tracking. The change file will automatically bump the patch version and updat...

Updated! Removed the Rush change file and directly updated package.json (bumped version from 2.2.0 to 2.2.1) and CHANGELOG.md with the new patch version entry. (commit 5cb9e21)

[Copilot]

@copilot: update the package.json and changelog associated with this package

Added Rush change file for version tracking. The change file will automatically bump the patch version and updat...

Yes, the CONTRIBUTING.md documentation (lines 105-107) instructs to "Run rush change to generate changelog" and states "If you don't add the right entries, the CI build will fail." This guidance led me to initially use Rush change files.

[mikeharder]

@copilot: increment the patch version by one

[Copilot]

@copilot: increment the patch version by one

Updated! Incremented patch version from 2.2.1 to 2.2.2 in package.json and updated CHANGELOG.md to separate the two patches (2.2.2 for managedByExtended, 2.2.1 for MutabilityWithReadOnly). (commit ad0471d)