Export components and hooks at root

[davidjgoss]

🤔 What's changed?

Components and hooks are now exported in a "flat" manner on the main entry point. Previously we exported components and hooks symbols which were objects containing components or hooks one or two levels deep.

⚡️ What's your motivation?

There was no real need to do this, since there are no naming collisions with any of the exported members. It also made the library harder to work with as a consumer, since editors tend not to work well with that non-standard way of exporting for auto-import etc.

🏷️ What kind of change is this?

• 🏦 Refactoring/debt/DX (improvement to code design, tooling, etc. without changing behaviour)
• 💥 Breaking change (incompatible changes to the API)

📋 Checklist:

• I agree to respect and uphold the Cucumber Community Code of Conduct
• I've changed the behaviour of the code
  • I have added/updated tests to cover my changes.
• My change requires a change to the documentation.
  • I have updated the documentation accordingly.
• Users should know about my change
  • I have added an entry to the "Unreleased" section of the CHANGELOG, linking to this pull request.

---

This text was originally generated from a template, then edited by hand. You can modify the template here.

[netlify]

✅ Deploy Preview for cucumber-react-preview ready!

Name	Link
🔨 Latest commit	4ed9ff6
🔍 Latest deploy log	https://app.netlify.com/sites/cucumber-react-preview/deploys/6818987ebb7a050008ec1e83
😎 Deploy Preview	https://deploy-preview-383--cucumber-react-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.