fix(azure-preview-workflow): update resource url to remove + use same token pattern

[cdransf]

Description

Verified: closed this PR, checked Azure admin and clean up succeeded. Pertinent run: https://github.com/adobe/spectrum-css/actions/runs/15788421553/job/44509686573

• Fixes failing removal portion of job by correcting URL param for remove command.
• Carries over logic from deploy step to clean and apply token when running remove command.

To-do list

• I have read the contribution guidelines.
• I have updated relevant storybook stories and templates.
• I have tested these changes in Windows High Contrast mode.
• If my change impacts other components, I have tested to make sure they don't break.
• If my change impacts documentation, I have updated the documentation accordingly.
• ✨ This pull request is ready to merge. ✨

[changeset-bot]

⚠️ No Changeset found

Latest commit: 102c2d7

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

[github-actions]

📚 Branch preview

PR #3979 has been deployed to Azure Blob Storage: https://spectrumcss.z13.web.core.windows.net/pr-3979/index.html.

[github-actions]

File metrics

Summary

Total size: 1.42 MB^*

🎉 No changes detected in any packages

* Size is the sum of all main files for packages in the library.
* An ASCII character in UTF-8 is 8 bits or 1 byte.

[pfulton]

I think this PR fixes the issue you were seeing. I do have one "let's check on this" thing: can you take a peek at Tarun's PR over in SWC and specifically the comments about passing some of these tokens around? I might be being overly cautious or paranoid, but if you could at least check on if these could be exposed/used in a risky way, that'd be appreciated!

[cdransf]

I think this PR fixes the issue you were seeing. I do have one "let's check on this" thing: can you take a peek at Tarun's PR over in SWC and specifically the comments about passing some of these tokens around? I might be being overly cautious or paranoid, but if you could at least check on if these could be exposed/used in a risky way, that'd be appreciated!

Updated in f703a86. Going to look at retrieving the new credentials in the AM. ✨