[Modules] Updated DeploymentExamples title & moved Bicep in front of JSON

[AlexanderSehr]

Description

• Updated DeploymentExamples title (now also showing the title of the file, instead of only a number)
• Moved Bicep in front of JSON
• Excluded new linter rule (which demands to define properties not with quotes where possible)

TODO:

• Underneath deployment examples header add a disclaimer: What do the example titles refer to, parameters are ordered, where is the cut to optional, etc.
• In the examples themselves (where is the split)

Pipeline references

For module/pipeline changes, please create and attach the status badge of your successful run.

Pipeline

Type of Change

Please delete options that are not relevant.

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Update to documentation

[github-actions]

Unit Test Results

  1 files  ±    0    1 suites  ±0   14s ⏱️ -51s
42 tests  - 358  42 ✔️  - 350  0 💤  - 8  0 ❌ ±0 
44 runs   - 357  44 ✔️  - 349  0 💤  - 8  0 ❌ ±0 

Results for commit 7d03399. ± Comparison against base commit 013bc47.

♻️ This comment has been updated with latest results.

[AlexanderSehr]

🍰

[itpropro]

Just adding my question from #1655 to have the discussion here.

Why are we not complying with Bicep best practices for the linter rule? When just importing some of the modules in a project, the current bicepconfig.json is probably not going to be copied or the project has it's own config. Also how does this behave with CARML modules consumed from a ACR?
I think we should comply with the Bicep linter wherever possible, what is the benefit in deviating from the linter rule, if it has downsides for all CARML customers that will receive warnings in their projects.
The linter rule itself adjusts the syntax to other languages like JavaScript.

[AlexanderSehr]

Just adding my question from #1655 to have the discussion here.

Why are we not complying with Bicep best practices for the linter rule? When just importing some of the modules in a project, the current bicepconfig.json is probably not going to be copied or the project has it's own config. Also how does this behave with CARML modules consumed from a ACR? I think we should comply with the Bicep linter wherever possible, what is the benefit in deviating from the linter rule, if it has downsides for all CARML customers that will receive warnings in their projects. The linter rule itself adjusts the syntax to other languages like JavaScript.

Replying similar to the comment in the other PR - let's rather do it all at ones in a PR designed for it, rather then a fractured way ;) #1664

[eriqua]

🆗