[SENTINEL] Use protocol deployment script for Sentinel

[philipandersson]

• Sort out dependencies in ethereum-contracts.

[philipandersson]

@0xdavinchee please sync with @d10r to unblock Sentinel GDA PR.

[d10r]

@0xdavinchee will provide a blueprint for how to do this, may require changes in protocol-monorepo.

We discussed how to minimize constraints put on the consuming application. Right now there's the following issues:

• The ethereum-contracts package doesn't specify the dependencies needed by dev-scripts/deploy-test-framework.js in its own package.json. Specifically hardhat and hardhat-ethers, which are required by that script, aren't included, they are instead included in the monorepo's root package.json. We don't know why that is. Those dependencies should either be moved to or duplicated into the ethereum-contract package.json. Open question: do they belong into "dependencies" or "peerDependencies"?
• The project using the deploy script may itself be a hardhat project and may use a different version, e.g. hardhat with ethers-v6 (which the deployment script expects ethers-v5). The script gets some objects provided by hardhat-ethers, e.g. here. If it just uses the hardhat environment provided by the consuming application, those objects may not have the shape the scripts expects in case of version mismatch. Thus even if the consuming application uses hardhat, it may be better for the deploy script to create its own hardhat environment and ethers objects. Currently open question: what should the interface look like? Right now it's just deployTestFramework with no arguments provided (but making assumptions about a pre-existing global environment).

[philipandersson]

We have a Fransktein's monster of a current setup for deployment. We are not blocked by this but it would be nice to align deployment scripts. We consider this tech debt for now.