fix: add further information to the README around the publishing workflow

[assadk88]

How to review this PR

Leave this text block for the reviewer

• Check component hierarchy is followed correctly
• Check the design Heuristics have been followed
• Check naming conventions have been applied
• Check for these gotchyas:
  • Missing exports for Oak components
  • Accidental export of Internal components
  • Snapshots of unexpected components have been modified
  • Circular dependencies
  • Code duplication (via not using base components)
  • Non-functional storybook for this or related components
  • Sensitve files changed eg. atoms, or style tokens
  • Relative imports
  • Default exports

Add your PR description below

Updated the README to contain extra information around the publishing workflow

Testing instructions

• Review the README changes and ensure clarity around the commit message conventions.
• Verify that the summary of commit types (patch, minor, major) aligns with the project's semantic release process.

ACs

• README accurately describes the Conventional Commits format for releases.
• Explanation of major, minor, and patch versions is clear and understandable.
• Reviewer is able to understand which commit messages trigger which type of release.

[netlify]

✅ Deploy Preview for lively-meringue-8ebd43 ready!

Name	Link
🔨 Latest commit	ad36f0e
🔍 Latest deploy log	https://app.netlify.com/sites/lively-meringue-8ebd43/deploys/66fe920e944c770008560bee
😎 Deploy Preview	https://deploy-preview-303--lively-meringue-8ebd43.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.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud