refactor(core-sdk): update core sdk to use contracts constant file

[kwiss]

Description

Breaking change

• Added chain id support in core & react SDKs
• Add chain id support in orderbook & executor contracts, updated corresponding tests
• Added createConfig in core & react SDKs to support one main config like in wagmi
• Updated exemple app to support chain switch with wallets
• Updated deployer to support contract deploy with chain id in constructor
• Updated react SDK ark provider to support base config from create config with optional params

What type of PR is this? (check all applicable)

• [ ] 🍕 Feature (feat:)
• [x] 🧑‍💻 Code Refactor (refactor:)

Related Tickets & Documents

Added tests?

• [x] 👍 yes

Added to documentation?

• [x] 📜 README.md
• [x] 📓 Documentation

Are there any post-deployment tasks we need to perform?

• [ ] ReactSDK: Add approve token for erc721 & erc20 with contract calls to check allowance https://github.com/ArkProjectNFTs/ark-project/issues/224
• [ ] CoreSDK: Fix tests with updated exemple scripts https://github.com/ArkProjectNFTs/ark-project/issues/245
• [ ] ReactSDK: Rename useRpc to useArkRpc and other stuff relate to ark that have a generic name https://github.com/ArkProjectNFTs/ark-project/issues/261
• [ ] ReactSDK: Create a generic way to retrieve & give arkAccount to the core functions https://github.com/ArkProjectNFTs/ark-project/issues/262

What gif best describes this PR or how it makes you feel?

PR Title and Description Guidelines:

• Ensure your PR title follows semantic versioning standards. This helps automate releases and changelogs.
• Use types like feat:, fix:, chore:, BREAKING CHANGE: etc. in your PR title.
• Your PR title will be used as a commit message when merging. Make sure it adheres to Conventional Commits standards.

Closing Issues

Fixes #247