Move submission to new BCeID

**Jira Ticket**: ALCS-1045

**Description**: As the land owner who has switched agents, I want my new agent to have access to my application in the Portal so if the local government returns my submission, someone can edit it.

*Acceptance Criteria*
* Identify the submission to be migrated
** ALC staff provides File ID; search on Applications, NOIs, and SRWs *ONLY*
** show the 
*** File ID
*** submitter's BCeID username
*** submitter's BCeID email address
*** submitter's BCeID business name (if available)
*** submitter's User UUID from ALCS
* Initiate move to new BCeID
** ALC staff hits 'Transfer'
* Input the new user UUID
** ALC staff provides the user's UUID
** Trim off spaces and require 36 characters in the field - show validation on the field
** Remind user they have to find the UUID in Metabase ([https://alcs-metabase-prod.apps.silver.devops.gov.bc.ca/])
* Confirms that the submission will be moved to from the old account to the selected new account
* Show error toast if File ID not found
* Show confirmation toast once transfer is successful

QA Notes:
* Check that ALC can still update Primary Contact via ALCS Edit Submission
* Check that L/FNG can still return to applicant
* Check that ALC can still return to LFNG
* Check that new BCeID can see the submission in their inbox
* Check that previous BCeID cannot see the submission in their inbox

Figma: https://www.figma.com/design/5qXmbgyOL5M8PO7m7oqCeR/ALCS?node-id=6104-96429&t=wu4VFySvnVkrHDcC-4 

**Last Updated**: 2025-03-04 10:54

Start by reviewing the Applications, NOIs, and SRWs search flows and the ALCS Edit Submission path, then inspect the Figma design and the Metabase UUID workflow. Done means ALC staff can find a submission, validate and transfer it to the new UUID, receive the specified success or error feedback, and the QA scenarios confirm access changes for both BCeIDs.

Written by the indexing model from the issue text.