use the same lock id between lock and unlock (#10039)

# Checklist for submitter

If some of the following don't apply, delete the relevant line.

- [ ] Changes file added for user-visible changes in `changes/` or
`orbit/changes/`.
See [Changes
files](https://fleetdm.com/docs/contributing/committing-changes#changes-files)
for more information.
- [ ] Documented any API changes (docs/Using-Fleet/REST-API.md or
docs/Contributing/API-for-contributors.md)
- [ ] Documented any permissions changes
- [ ] Input data is properly validated, `SELECT *` is avoided, SQL
injection is prevented (using placeholders for values in statements)
- [ ] Added support on fleet's osquery simulator `cmd/osquery-perf` for
new osquery data ingestion features.
- [ ] Added/updated tests
- [ ] Manual QA for all new/changed functionality
  - For Orbit and Fleet Desktop changes:
- [ ] Manual QA must be performed in the three main OSs, macOS, Windows
and Linux.
- [ ] Auto-update manual QA, from released version of component to new
version (see [tools/tuf/test](../tools/tuf/test/README.md)).

cmd/fleet/vuln_process.go

@@ -95,7 +95,7 @@ by an exit code of zero.`,
 					"failed to obtain vuln processing lock, something else still has lock ownership")
 			}
 			defer func() {
-				err = ds.Unlock(ctx, "cron_vulnerabilities", "vuln_processing_command")
+				err = ds.Unlock(ctx, string(fleet.CronVulnerabilities), "vuln_processing_command")
 				if err != nil {
 					initFatal(err, "failed to release vuln processing lock")
 				}