Bug: custom collider props are not reactive anymore.

[Neosoulink]

Describe the bug

While working on the Joint I wanted to reproduce the same custom collider exportation, and when I wanted to watch the Joint props, I wasn't able to do so...

I figured that the Vue component setup function needs a Proxy as the first parameter to reflect changes and here:
https://github.com/Tresjs/rapier/blob/main/src/components/colliders/index.ts#L29-L42

props: {
      ...BaseCollider.props,
      shape: undefined,
    },
    setup(props, ctx) {
      return {
        ...BaseCollider?.setup?.(
          { ...props, shape } as Parameters<
            Exclude<(typeof BaseCollider)['setup'], undefined>
          >['0'],
          ctx,
        ),
      }
    },

We are destructing it which is equivalent to passing a native Object

Reproduction

---

Steps to reproduce

---

System Info

---

Used Package Manager

npm

Code of Conduct

• I agree to follow this project's Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• The provided reproduction is a minimal reproducible example of the bug.

[Neosoulink]

I'm going to provide a fix asap @alvarosabu @JaimeTorrealba