Feat: enable agent to use mTLS communication

[yungcero]

This pull request introduces a feature to the hashtopolis agent-python that allows the option for the agent to use mTLS verification in its session with the hashtopolis server. This is helpful if the hashtopolis server is configured to use mTLS for additional security.

By default it will be disabled unless someone has the need/use case to enable mTLS comms. The changes take advantage of the use of the requests.session class that is being used to handle client/server communication.

Also whitespace is stripped and single ticks '' have been changed to quotations "" due to my editor.

[yungcero]

@s3inlc thoughts on this feature?

[brandoncasaba]

This is already the --cert flag for specifying a client cert

[yungcero]

Yes, but unless the client key is bundled in with the cert file, it won't work since the -- cert argument does not allow tuples of client/key. Perhaps a better change would be to allow that option? In addition, I don't think there's a current way to add in a CA file which this change includes. For some background - my use case was that I would spin up some containers, use some scripts to remote into it and then deploy this agent with the certs to my server. It was easier for me to pass in the CA file than to update every host im remoting into