Allow entrypoints by default

[bossmc]

Why this change?

Following the principle of least surprise, don't suppress image entrypoints unless asked to.

Relevant testing

Tested with an image that runs an entrypoint before starting the image.

Checks

These aren't hard requirements, just guidelines

• New/modified Rust code formatted with cargo fmt
• Documentation and README.md updated for this change, if necessary
• CHANGELOG.md updated for this change

[maxdymond]

LGTM but would like a review from Richard as well.

[rlupton20]

Fine by me. I'm not 100% what is the least surprise to people - I think most users, for whatever reason, think floki is some magic thing which always gives you an interactive session in any docker container (hence entrypoint suppression, and shell as the default entrypoint - to the first approximation the thing most likely to achieve this).

Equally, most containers don't have weird entrypoints that need supressing (especially the ones floki is used with). For those that do, having the override is important. It's probably more reasonable that most containers behave as they normally do, so entrypoint override by default I suppose is a default created by the rare case, so more suprising. I don't know.

Anyway, happy with the change - one small thing on the default shell (which to be honest was probably as you've written for ages already anyway).

[maxdymond]

I've deprecated the actions-rs Github Actions as they are not being actively maintained - you might need to tweak your MR so that you're using the new code.