fix: replace hard coded components path with the resolved path

[Slartibartfass2]

Closes #1532

Previously, anybody who didn't use the default components.json couldn't execute the update because if the ui path had been changed, this would resolve in an exception. Now the resolved alias path from the components.json is used.

Before submitting the PR, please make sure you do the following

• If your PR isn't addressing a small fix (like a typo), it references an issue where it is discussed ahead of time and assigned to you. In many cases, features are absent for a reason.
• Prefix your PR title with feat:, fix:, chore:, or docs:.
• This message body should clearly illustrate what problems it solves.
• Format & lint the code with pnpm format and pnpm lint

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6890047

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[Slartibartfass2]

@huntabyte Hi there, is there any problem with this PR? It has been a while since it was opened.

[huntabyte]

Hey @Slartibartfass2, we have reworked a lot of the internals of the CLI in the next-tailwind-4 PR to support custom registries and whatnot. @AdrianGonz97 what do you think about this?

[AdrianGonz97]

Apologies for the delay! This should already be resolved as of [email protected]