ci: always update lockfile regardless of whether changeset already exists

[phoenix-server]

Follow-up to #656.

When workflow_dispatch is run against an existing dependabot PR that already has a changeset, the lockfile should still be updated. Previously the commit was gated on a single CHANGED flag that could leave the lockfile uncommitted.

• Tracks ADDED_CHANGESET and ADDED_LOCKFILE independently
• Commits (and pushes) whenever either is true
• Commit message reflects what was actually added

[changeset-bot]

⚠️ No Changeset found

Latest commit: d2df259

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