Add default tags to Bicep examples

[brooke-hamilton]

Description

Updated Bicep examples to add the same tags as the base MLZ Bicep deployment. Users can supply an optional parameter to add tags, and the example will union those tags with the standard MLZ tags.

I considered adding a new module for calculating the tags, like this:

targetScope = 'subscription'

param tags object = {}
var defaultTags = {
  'DeploymentType': 'MissionLandingZoneARM'
}
var calculatedTags = union(tags, defaultTags)

output tags object = calculatedTags

Which would be called from another template like this:

param tags object = {}
module calculatedTags '../../modules/calculateTags.bicep' = {
  name: 'calculatedTags'
  params: {
    tags: tags
  }
}

The advantage would be that it's a single place to manage the default tags. However, I didn't use it because the amount of code required to call the module was not much less than the code to do the calculation within each template. I'm open to changing my mind if others have a different opinion. 👍

Issue reference

The issue this PR will close: #580

Checklist

Please make sure you've completed the relevant tasks for this PR out of the following list:

• All acceptance criteria in the backlog item are met
• The documentation is updated to cover any new or changed features
• Manual tests have passed
• Relevant issues are linked to this PR

[glennmusa]

I considered adding a new module for calculating the tags, like this:
[...] However, I didn't use it because the amount of code required to call the module was not much less than the code to do the calculation within each template. I'm open to changing my mind if others have a different opinion. 👍

I agree with leaving the union implementation in the examples.