Add support for Hishtory/Atuin

[iamkirkbater]

For a feature to be complete, it should have:

• Functional changes completed
• Unit tests on at least 80% of the code in the feature
• Config file changes documented in the migration guide
• Documentation completed for the feature within the docs/features folder

When building a feature - consider the user-experience as the foremost responsibility. Once we cut the v1.0.0 release - we are "locked" into flags and arguments that we accept.

Example:

• if a user has NOT explicitly enabled or configured an optional feature and it does not work out of the box - log out to info as to why (as the default log level is warning). This allows the program to "just work".
• However, if the user HAS provided some configuration and it's not working - log out to Warning that it isn't working so that we're explicit as to why something isn't working.

With this in mind, this issue tracks the ability to configure Hishtory/Atuin support within ocm-container.

User Story:

• As an SRE using ocm-container, I want to be able to query commands that I may have run on other containers, even if they're not directly in my current container's history.
• As an SRE using ocm-container who is being questioned about actions I took on a particular cluster at a particular time - I'd like to be able to get an idea of what I was doing on a given cluster at a given time.