Long Input Entries Cause Potential Performance and UI Issues

[ofahimIQSS]

Description:
While testing the related pull request locally, an issue was observed with the "Registration" page when users enter an excessively long input in the Affiliation and Position fields. The long inputs could potentially cause performance issues, as well as degrade the user experience.

Steps to Reproduce:
Follow the test steps in the pull request.
Navigate to the Registration page using the test account credentials:
Email: [email protected]
Password: curator
In the Affiliation field, enter a very long entry (e.g., "Harvard University") and repeat/paste it multiple times to create a string of 1,000+ characters.
In the Position field, enter a very long entry (e.g., "Affiliate") and repeat/paste it multiple times to create a string of 1,000+ characters.
Click on Create Account.

Observed Behavior:
The form processes the inputs, but there is no restriction on the character length for these fields.
This may lead to performance bottlenecks or unexpected UI behavior.

Expected Behavior:
The input fields should have a sensible character limit to prevent performance and usability issues.

Questions for Discussion:
Should we impose a maximum character limit on the Affiliation and Position fields?
If so, what should the limit be (e.g., 255 characters)?

Suggested Fix:
Add input validation to both Affiliation and Position fields to enforce a character limit.
Implement server-side validation to ensure data integrity in case of API misuse.

[pdurbin]

I'm just adding the nice screenshot from #558 (comment)

[g-saracca]

@GPortas we will probably need a dataverse repo issue for this also right?