Admin UI Force Unlock button on create for auth collections

[DanRibbens]

Bug Report

The "Force Unlock" button is visible on create for auth collections.

Expected Behavior

The button should be disabled so you can see where it is for later use.

Current Behavior

The button is not disabled and when clicked it and it makes a non-sense request to unlock a user without sending the needed email address, returning a 500 status.

Possible Solution

Instead of disabling, we could hide it. I prefer to disable it for UX.

Steps to Reproduce

1. Have a collection that includes auth
2. From the admin panel, go to create a new item in the collection
3. Click the "Force Unlock" button

Detailed Description

payload v0.2.9

[github-actions]

This issue has been automatically locked.
Please open a new issue if this issue persists with any additional detail.