fix: Fixed MSI UDT test to only check for the required output if the imported type is also used by a parameter

[AlexanderSehr]

Description

We currently have the case that the elastic-san module failed because one of its child-modules (volume-Group) has a managedIdentities parameter which is imported into the parent elastic-san module for the type of the volume-group. Now, this adds the managedIdentityAllType to the defintions section of the parent module.
The tests found this declaration and assumed the type is used and because it supported the systemAssignedIdentity property, it required the systemAssignedMIPrincipalId, which in this case is incorrect. The child needs it, not the parent.

I updated the test so that it not only checks if the UDT is declared, but if it's also used by a parameter in the same module.

Tested

• Automation-Account: Worked
• Automation-Account with removed output: Failed as expected
• Elastic-San: Worked

Pipeline Reference

Pipeline
(unrelated issue (in main))
(unrelated issue (in main))
(unrelated (in main))
(unrelated (in main))
(unrelated (in main))

Type of Change

• Update to CI Environment or utilities (Non-module affecting changes)
• Azure Verified Module updates:
  • Bugfix containing backwards-compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json:
    • Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
    • The bug was found by the module author, and no one has opened an issue to report it yet.
  • Feature update backwards compatible feature updates, and I have bumped the MINOR version in version.json.
  • Breaking changes and I have bumped the MAJOR version in version.json.
  • Update to documentation