Circleci project setup

[Dargon789]

Summary

Briefly describe what this change introduces.

Type of change

• New Feature - A change that adds functionality.
• Bugfix - A change that resolves an issue.
• Tweak - A change that modifies existing features.
• Refactor - Code improvements without changing behavior.
• Performance - Optimizations for gas or execution efficiency.
• Documentation - Updates to docs, comments, or NatSpec.
• Tests - Adding or updating test coverage.
• Chore - Maintenance, dependencies, CI/CD, deployments or tooling updates.

Details

Provide any additional details if needed.

References

Link any existing PRs, such as SDK PRs related to this PR, or any additional references.

Checks

For New Contracts

• Does the new contract have tests?
• Does the contract contain all the NatSpec needed (@title, @notice, @param, etc.)?
• Is the contract deployed and the address added to the JSON file?
• If the contract is registered, is the waitPeriod set correctly?
• Is the contract verified and added to the Tenderly dashboard?
• Is documentation written for the corresponding DFS action and added to GitBook?

For Modifications to Existing Contracts

• If there were existing tests for the contract, are they adapted for the change and executed?
• Is the contract redeployed and added to the JSON file?
• If the contract is registered, is the waitPeriod set correctly?
• Is the contract verified and added to the Tenderly dashboard?
• If some parameters were changed and a breaking change was introduced, is the documentation updated on GitBook?

For Strategies

• Are new tests added for the strategy?
• Is the strategy deployed and added to the JSON file?

Summary by Sourcery

CI:

• Add initial CircleCI config with a simple docker-based job and workflow to validate pipeline setup.