Unlock requirements are overly strict

[mwarkentin]

People other than the original author should be able to unlock PRs / slices. Currently this requires going outside of TACOS and using the CLI to do a terraform force-unlock.

With our distributed company, this can block someone for hours to a day depending on who has a lock.

tf-lock-release: failure: not [email protected]: .([email protected])

Alternative, keep the existing functionality but have a force-unlock option to bypass this check.

[lynnagara]

here's an example: https://github.com/getsentry/ops/pull/11643#issuecomment-2263819530

i was trying to help a user with an ops request by requesting a plan on someone elses PR. This locked the PR so all future commits failed and attempts to unlock also failed due to this lock. It had to be manually unlocked over CLI.