ci: notify nuxt/bridge when composables change

[wattanx]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

The composables in nuxt/bridge are ported from nuxt 3.
So, if there are changes in nuxt 3, we need to follow the changes.
In the workflow being added this time, if composables are modified in Nuxt 3, a notification will be sent to nuxt/bridge.

nuxt/bridge is already set up to receive notifications.
nuxt/bridge#1013

(I would like to discuss if this name for the workflow is appropriate.)

Todo

• Secrets must be prepared.
  • Need to add contents: read & write for nuxt bridge repo.
  • metadata: read only (automatically selected when selecting the contents permission)

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[danielroe]

this looks 👌

[wattanx]

@danielroe
Could you create a Personal Access Token (PAT) to be used in Actions?
(It is needed to add permissions to nuxt/bridge.)

• In the case of a fine-grained personal access token:
  • need contents: read & write and metadata: read only permissions.
• In the case of a classic PAT:
  • need repo scope

https://github.com/peter-evans/repository-dispatch?tab=readme-ov-file#token

(In the code, it is set to ACCESS_TOKEN.)