Streamline tag tests

[Klaas-]

SUMMARY

in #1964 @Fred-sun and me spend quite a long time looking at how tags behave and should behave in the azure collection. The outcome is a (hopefully) complete test suite how tags should work that can/should be adopted into other modules that offer tag/append_tags support.

Essentially the test should be (always + idempotency verification)

1. Creation of a resource without tags
2. Creation of a resource with tags
3. Adding a tag to 1)
4. Adding another tag to 1) with explicit append_tags: true
5. Replacing existing two tags on 1) with a different tag (append_tags: false)
6. Remove tags (append_tags: false and tags unset)

ISSUE TYPE

• Feature Idea

COMPONENT NAME

All resources that use tags

ADDITIONAL INFORMATION

It seems that tags on azure level are not properly streamlined: Azure/azure-rest-api-specs#35693 so there may be slight variations needed in the tests like in #1971

[Fred-sun]

When developing, everyone can test this in this way. The functions will be more comprehensive. Thank you!

[Fred-sun]

@Klaas- I think this is more like a notice on how to test the tags attribute. It cannot be regarded as a bug. A Pull Requrest can be proposed to update readme.md. Thank you!

[Klaas-]

Yeah, I don't see this as a bug, its a feature request for more test coverage for existing modules and maybe we can make it part of the developer docs for new modules to at least include those tests for tag support.