feat: Add database tags per az, feat: Add public and private and database tags per cidr

[kahirokunn]

Description

Motivation and Context

Breaking Changes

How Has This Been Tested?

• I have updated at least one of the examples/* to demonstrate and validate my change(s)
• I have tested and validated these changes using one or more of the provided examples/* projects

• I have executed pre-commit run -a on my pull request

[github-actions]

This PR has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this PR will be closed in 10 days

[kahirokunn]

keep

[bryantbiggs]

thank you but this is not something we will be adding to the module at this time

[kahirokunn]

@bryantbiggs May I ask why you don't tag them?

[bryantbiggs]

because its not a pattern we commonly see used nor do I think its a pattern that we would want to promote (in the world of IPAM and dynamic IP assignment, this will fail horribly)

[kahirokunn]

@bryantbiggs #901

If so, how about this one?
I feel this style of code is common.

[bryantbiggs]

that PR is entirely different - it does not rely on computed values as keys to a map

[kahirokunn]

I see. Thx.

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.