fix: change deps versions from "workplace" to "^0.1.0"

[thetarnav]

• Change dependency versions of packages from "workspace^" to "^0.1.0" (current version) — Fixes  No matching version found for @solid-aria/types@* inside the workspace #29
  0.1.0 instead of 0.1.1 because changesets should update those

• Move solid-primitives packages from peerDependencies to dependencies.
  Those are normal dependencies. This may cause missing peerdependency warnings during installs (in this repo), to do that we'd have to add "solid-js" as dev dependency everywhere, but I just didn't have the strength to do it. The warnings are harmless anyway...

[changeset-bot]

🦋 Changeset detected

Latest commit: 2ca4cfc

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 23 packages

Name	Type
@solid-aria/breadcrumbs	Patch
@solid-aria/button	Patch
@solid-aria/checkbox	Patch
@solid-aria/collection	Patch
@solid-aria/dialog	Patch
@solid-aria/focus	Patch
@solid-aria/i18n	Patch
@solid-aria/interactions	Patch
@solid-aria/label	Patch
@solid-aria/link	Patch
@solid-aria/list	Patch
@solid-aria/listbox	Patch
@solid-aria/menu	Patch
@solid-aria/overlays	Patch
@solid-aria/primitives	Patch
@solid-aria/radio	Patch
@solid-aria/selection	Patch
@solid-aria/switch	Patch
@solid-aria/toggle	Patch
@solid-aria/tree	Patch
@solid-aria/types	Patch
@solid-aria/utils	Patch
@solid-aria/visually-hidden	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[fabien-ml]

If we put solid-primitives as deps instead of peer deps, user may have version conflict when trying to install them.

[thetarnav]

And having them as peer solves that? Don't package managers take care of that already?
If we don't update deps there will be issues with incompatible versions anyway.
solid-primitives are just normal dependencies that are necessary, the user shouldn't have to worry about installing/managing them
If you were using clsx, would you put it as a peer dependency? That doesn't make sense...