feat: adds time range module

[linnall]

Pull Request Checklist

• Did you add new tests and confirm existing tests pass? (yarn test)
• Did you update relevant docs? (docs are found in the site folder, and guidelines for updating/adding docs can be found in the contribution guide)
• Do your commits follow the Conventional Commits standard?
• Does your PR title also follow the Conventional Commits standard?
• If you have a breaking change, is it correctly reflected in your commit message? (e.g. feat!: breaking change)
• Did you run lint (yarn lint:check) and fix any issues? (yarn lint:write)
• Did you follow the contribution guidelines?

---

PR-Codex overview

This PR introduces the TimeRangeModule, which provides functionality to manage time-based validation in a smart contract environment. It includes methods for encoding installation and uninstallation data, and integrates this module into the existing testing framework.

Detailed summary

• Added TimeRangeModule with metadata and ABI.
• Implemented encodeOnInstallData, encodeOnUninstallData, and encodeSetTimeRange methods.
• Updated tests to include installation and uninstallation of the TimeRangeModule.
• Verified the use of valid time ranges during the installation process.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
aa-sdk-site	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 20, 2024 5:31pm
aa-sdk-ui-demo	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 20, 2024 5:31pm

[graphite-app]

How to use the Graphite Merge Queue

Add the label graphite-merge-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

[linnall]

closing this pr because the commit history is a mess. changes have been moved to #1253