fix link card dialog

[arsforza]

AB#39408

Describe your changes

• fixed tokenCode passed with dashes ("-") exceeding the character number limit (19)
• fixed dialog not hiding via X and backdrop click
• refactored template
• added to the frontend a check for tokenCode already assigned to current registration (it was throwing and unhandled 500 error)

Checklist before requesting a code review

• I have performed a self-review of my code
• I have addressed all Copilot comments
• I have asked the design team to review these changes, or: The changes do not touch the UI/UX
• I have added tests for my changes, or: Adding tests is unnecessary/irrelevant
• I have made sure that all automated checks pass before requesting a review
• I have updated all documentation where necessary
• I have checked the list of integrations with the 121 API for changed endpoints
• I do not need any deviation from our PR guidelines

Portal preview-deployment

https://happy-rock-0411d2003-7680.westeurope.3.azurestaticapps.net

[elwinschmitz]

There is some overlap with the review of:
#7655 (review)

[elwinschmitz]

This is 'just a pure function', right?
Does it need to be computed at all?

I don't think we need a lot of that Signal-magic-dust here...

[elwinschmitz]

Also; I think we can even check for a bigger range of "weird characters people will use";

So we could "remove everything that is not a digit", by:

Suggested change

	}) => computed(() => tokenCodeToClean.replaceAll('-', ''));
	}) => computed(() => tokenCodeToClean.replace(/\D/g, '');

So it would catch (double) spaces, dashes, underscored, periods, comma's, etc...

[elwinschmitz]

Would there be a safety-value for the min-width? Or a valid max-width?

That way, this dialog would became a lot more "safe for responsive use"...