feat: Use a map for root_block_device instead of list

[Yethal]

Description

root_block_device variable is now a map instead of list of maps.

Motivation and Context

Since aws_instance resource only allows for a single root_block_device it makes no sense to use a list since it will only ever accept a single element. Moreover storing this configuration in a map instead of wrapping it with a list will make it easier to use with Terragrunt and deep merged configs

Breaking Changes

Yes

Streamline and simplify usage with wrapping automation

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

[Yethal]

@antonbabenko Can we merge this?

[antonbabenko]

This breaking change brings little improvements, so I don't think we need to introduce it now. Maybe in the future (during the next major release).

[ThickDrinkLots]

upvote

[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

[Yethal]

unstale
I'd like to keep this open so it gets merged together with whatever change bumps the major version number

[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

[Yethal]

unstale

[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

[Yethal]

unstale

[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

[Yethal]

unstale

[Yethal]

@antonbabenko how about a major release on New Year?