chore: release v1.7.2

Merge branch 'release/1.7.2' into issue-1466

Merge pull request #1693 from formkit/fixing-issue-1481

fix(vue): capture scope at createSlots time for $cmp children

fix(nuxt): resolves #1660

Merge branch 'release/1.7.2' into fixing-issue-1481

Merge pull request #1692 from formkit/fixing-issue-1481

fix(vue): allow $cmp children to access parent scope data

chore: release v1.7.1

chore: use exact versions for pre-release @formkit dependencies

When publishing pre-releases (next/dev), convert workspace:^ to exact
versions instead of caret ranges. This prevents semver from resolving
to a "higher" hash that's actually an older release.

The issue: ^1.7.1-next.acd337a can match 1.7.1-next.d067e54 because
'd' > 'a' in semver pre-release comparison, even though acd337a was
published later with newer code.

fix: pre-release publishes no longer commit version changes

For next/dev releases:
- publish.mjs now only creates and pushes a tag (no version commit)
- Package versions remain unchanged in the repo

For CI (ci-publish.mjs):
- Added --version flag to set package.json versions before publishing
- Pre-release versions are detected and applied at publish time
- This allows publishing from tags without committed version changes

Master branch releases continue to work as before:
- Versions are written to package.json
- Changes are committed with the release tag

chore: release v1.7.1-next.d067e54