[Feature Request]: Enable new dependency approach from a pipeline perspective

[AlexanderSehr]

Description

This issue should track our progress to enable the new dependency approach documented als 'Variant 5' here (#329).

This means

• The pipeline should (side-by-side with the original approach) support .bicep test files on top of the .json test files (both for GitHub & Azure DevOps). This is important as reworking the modules to the new dependency approach will take time and cannot happen as a big-bang
• The new .bicep test files will deploy not only the parent template (module <resourceType> '../deploy.bicep'), but also the dependencies required for the given test case

  Note: We should not use our own modules to deploy dependencies but raw resource deployments. However, we may centralize common patterns (e.g., for dependency resources) in centralized files.

• The .parameter folder should be renamed to something more appropriate. This should happen in the predecessor [Feature Request] BREAKING change: Rename .parameters folder to .test #1577.

[itpropro]

I think it's great to start with the pipelines and then go through the change in multiple iterations. As for the folder rename, I think we should go with .test as folder name, as it would comply to most OSS frameworks and tools as well as development languages. Even if we have multiple types of tests in there, we can easily distinguish them by name or folder.
Is there anything I can do to support in the process? I have two new modules as PRs open, would these be a good opportunity to test the new .bicep test files already?

[AlexanderSehr]

Hey @itpropro, let's discuss the folder naming in the predecessor issue #1577 . I'll add some more detail there too