feat(contract): explore the possibility to use a fully onchain orderbook on

[ptisserand]

Description

1. Orderbook is now a component
2. Remove messaging in Starknet part
3. Add version and order_type in Orderbook component events
4. Move dependencies version to workspace Scarb.toml
5. Update to cairo 2.7.1, snforge 0.28 & OZ 0.15.1

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

• 🍕 Feature (feat:)
• 🐛 Bug Fix (fix:)
• 📝 Documentation Update (docs:)
• 🎨 Style (style:)
• 🧑‍💻 Code Refactor (refactor:)
• 🔥 Performance Improvements (perf:)
• ✅ Test (test:)
• 🤖 Build (build:)
• 🔁 CI (ci:)
• 📦 Chore (chore:)
• ⏩ Revert (revert:)
• 🚀 Breaking Changes (BREAKING CHANGE:)

Related Tickets & Documents

Added tests?

• 👍 yes
• 🙅 no, because they aren't needed
• 🙋 no, because I need help

Added to documentation?

• 📜 README.md
• 📓 Documentation
• 🙅 no documentation needed

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

[optional] 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

[changeset-bot]

⚠️ No Changeset found

Latest commit: 002f42e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[linear]

DEV-762 Explore the possibility to use a fully onchain orderbook on starknet