Adding serialization functionality and multion examples

[HowieG]

• Fixing tuple (only available in python3.9+) to Tuple (from typing module)
• Changing auto_start_session default to True only if init() was explicitly called. Otherwise had bug where initializing Client singleton with record_function() would auto_start_session when it was just being decorated. Meaning partner frameworks where agentops was integrated but optional (e.g. multion) would try to start_session() even if user didn't explicitly use agentops.
• Automatically assigning screenshot from returns.screenshot to ActionEvent.screenshot for convenience for partners (multion)
• Updating safe_serialize to also call any available json(), to_dict(), or dict() formatting functions
• Updating remove_none_values to remove_unwanted values (None, ... (ellipsis which multion OMITs), and self)

[gitguardian]

⚠️ GitGuardian has uncovered 6 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
10824647	Triggered	Generic High Entropy Secret	faad6a8	docs/mint.json	View secret
10824647	Triggered	Generic High Entropy Secret	775e6e0	docs/mint.json	View secret
11373238	Triggered	Generic High Entropy Secret	870cf9b	examples/multion_step_session_example.ipynb	View secret
11373238	Triggered	Generic High Entropy Secret	7468115	examples/multion_step_session_example.ipynb	View secret
11373239	Triggered	Generic High Entropy Secret	870cf9b	examples/multion_step_session_example.ipynb	View secret
11373239	Triggered	Generic High Entropy Secret	7468115	examples/multion_step_session_example.ipynb	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

Shawn+Braelyn on board for auto_start_session