feat(contracts): Refactor dependency routing to ensure seamless usability from importer contract repos

[ethenotethan]

Why are these changes needed?

To Ensures contracts can be publicly hosted in a way that's cross compatible with foundry and hardhat projects when imported. Currently this was tested/validating using nitro-contracts. Also to Introduce some level of release mgmt to our contracts.

Changes

• Added yarn as a dependency to our contracts for version mgmt
• Refactored all submodule import paths to raw file schema
• Reworked remappings.txt to not alias submodule dependencies
• Set OZ dependencies as JS ones since referencing via submodule imports would cause type collisions with other submodules with OZ in nested dependency graph (e.g, eigenlayer-middleware importing @open-zeppelin/ERC20)
• Called out some hygiene todos in test-contracts CI
• Modified test-contracts CI job to install JS/yarn dependencies as prequisite before running tests

Follow up todo(s):

• Build automation or framework for performing contract releases

Methodology

Played around with hosting the contracts via npm directly from the monorepo. The main issue that was causing dependency conflicts in rollup contract repos that utilize hybrid foundry x hardhat was that foundry uses a remapping.txt to provide shortcut aliasing for dependency contract paths. Hardhat doesn't acknowledge this however unless you use the hardhat x foundry plugin which requires careful re-articulation of each rollup contract repo's yarn dependency graph. This isn't particular pretty but it does remove the need to manually manage https://github.com/Layr-Labs/eigenda-utils/ while providing some level of version management for our contracts. Opening for discussion if this is something we'd wanna pursue and if so will continue to clean up. We should ideally be cutting release for our contracts in-accordance to when we perform on-chain upgrades or make key updates to the verification utils / blob verifier. The new npm library can be found here with reference usage here in nitro-contracts.

Checks

• I've made sure the tests are passing. Note that there might be a few flaky tests, in that case, please comment that they are not relevant.
• I've checked the new test coverage and the coverage percentage didn't drop.
• Testing Strategy
  • Unit tests
  • Integration tests
  • This PR is not tested :(