[deejgregor]

This has a few small changes related to startup checks:

• Log a warning if the container image and server architectures do not … -- see discussion in https://testcontainers.slack.com/archives/C1SUBPZK6/p1672168624784639
• Make sure a container exiting successfully is properly handled -- I stumbled across this bug while testing the above item, and I also added a test
• We don't need to continue checking if the container stops running -- Ran into this in one of our systems when we had an error where something exited early but it would still continue checking until the startup timeout expired
• Add a section covering the container startup lifecycle -- I think it could make sense to more clearly state the order of the startup lifecycle. Note: I'm not sure if it makes sense to include each of these items (in particular, the methods that are available for subclasses to override, as well as the wait for the exposed port check), but I included them here for completeness.

[eddumelendez]

Thanks for raising the PR, @deejgregor ! I've left some comments

[eddumelendez]

Thanks for your contribution, @deejgregor ! This will be part of the next release