Update amazon-ssm-agent systemd unit files to start after important services on boot

[thimslugga]

Issue #, if available:

Description of changes:

The Amazon SSM Agent should be started after networking and dns available and should not start until after cloud-init has finished to prevent yum/dnf lock contention like issues.

• https://systemd.io/NETWORK_ONLINE/
• https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/

There's numerous threads of AL2023 and lock contention issues.

• https://repost.aws/questions/QU_tj7NQl6ReKoG53zzEqYOw/amazon-linux-2023-issue-with-installing-packages-with-cloud-init
• https://repost.aws/questions/QULl6jRiWxQpiefbOfGcObdg/linux-error-another-app-is-currently-holding-the-yum-lock-waiting-for-it-to-exit-the-other-application-is-yum

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.