feat: Add lifecycle ignore userdata as otherwise reboots existing instances

[adavis-sdx]

Description

Add instance Lifecycle rule to ignore user_data changes.

Motivation and Context

There are times when I want to update the userdata and not replace the existing instances (which can be achieved with user_data_replace_on_change) but also not reboot the existing instances which is the case if not replaced. We can't be rebooting tens of instances for a small change we want applied to any new instances and if we want it applied to all instances then a replace is required anyway

Breaking Changes

No

How Has This Been Tested?

• [ X] I have updated at least one of the examples/* to demonstrate and validate my change(s)
• [X ] I have tested and validated these changes using one or more of the provided examples/* projects
• [X ] I have executed pre-commit run -a on my pull request

[adavis-sdx]

Sorry, I know it is not good having more resources just to be able to add this "lifecycle ignore" entry but as it is not possible to pass anything but a static list it would seem like the only way. I would have loved to make it dynamic if that was supported.

[bryantbiggs]

unfortunately, this doesn't make sense. perhaps a different architecture is better suited (i.e. - using autoscaling groups)

[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.