Fix sdk module test issue

[vidai-msft]

Description

This PR fixes the issue when a SDK based module had multiple test projects, PR validation only ran the .Test.
Instead all of the *.Test projects should be run

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
  • No need for a release

• 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.
  • 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
• SHOULD have proper test coverage for changes in pull request.
• SHOULD NOT adjust version of module manually in pull request

[azure-client-tools-bot-prd]

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

[Copilot]

Pull Request Overview

This PR adjusts the test project discovery in Get-CsprojFromModule to find and include all *.Test.csproj files under each module’s test directory, rather than only the <Module>.Test project. It also cleans up semicolons and standardizes some control‐flow formatting.

• Broaden test csproj lookup via Get-ChildItem pipelines
• Remove trailing semicolons in hashtable and return statements
• Normalize brace placement in else blocks

Comments suppressed due to low confidence (2)

tools/BuildScripts/BuildScripts.psm1:9

• [nitpick] Indentation for the 'Storage' entry doesn’t match the surrounding entries. Consider aligning keys consistently for readability.

        'Storage'     = @('Storage.Management')

tools/BuildScripts/BuildScripts.psm1:66

• [nitpick] The else keyword is on its own line. For consistency with the rest of the script, consider merging } and else onto one line as } else {.

        else {