corrected devcontainer to work on arm64 computers

[RenSilvaAU]

Description

Updated devcontainer configuration for Azure PowerShell development

The configuration includes:

• Custom Dockerfile based on .NET 8.0 SDK (amd64 platform)
• GitHub CLI and Node.js LTS features
• Post-create script that installs AutoRest, platyPS, and Az.Accounts modules
• C# extension pre-configured for the container
• Root user access for PowerShell script execution

Mandatory Checklist

• Please choose the target release of Azure PowerShell. (⚠️Target release is a different concept from API readiness. Please click below links for details.)

  • [ ] General release
  • [ ] Public preview
  • [ ] Private preview
  • [ ] Engineering build
  • [x] No need for a release

• [x] Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

• SHOULD update ChangeLog.md file(s) appropriately
  • Update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense. not the case
  • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
• SHOULD regenerate markdown help files if there is cmdlet API change. [Instruction] (../blob/main/documentation/development-docs/help-generation.md#updating-all-markdown-files-in-a-module) not the case
• SHOULD have proper test coverage for changes in pull request. not the case
• SHOULD NOT adjust version of module manually in pull request not the case

[azure-client-tools-bot-prd[bot]]

Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status.

[RenSilvaAU]

@dolauli ,

Isolated change for devcontainer, as suggesed in previous PR

[wyunchi-ms]

/azp run

[azure-pipelines[bot]]

Azure Pipelines successfully started running 3 pipeline(s).