chore: align how IBAN validators messages work with other validators

[ryubro]

What I did

1. Aligned the way how the messages of IBAN validator is loaded with other validators
   • While many other validators override getMessage() class method by calling separate functions, IBAN validators override getMessage() instance method which loads its own translation messages
     • As the result, current IBAN validators show default messages without calling loadDefaultFeedbackMessages() while many other validators show the fallback messages like:

       Please configure an error message for "xxx" by overriding "static async getMessage()"

     • By aligning IBAN validators with others, now IBAN validators don't show default messages without calling loadDefaultFeedbackMessages() or loadInputIBANMessagesNoSideEffects() which is a BREAKING CHANGE
2. [boy-scouting] Add missed loadDefaultFeedbackMessages() to input-email document

Why

While checking an old issue about IBAN error message (#1783), I found we can override the error message by doing:

IsIBAN.getMessage = () => 'Vul een geldige Rekeningnummer in.';

html`
  <lion-input-iban .modelValue=${'NL20INGB0001234567XXXX'}></lion-input-iban>
`;

but this requires the consumer of the component to know the implementation details that IsIBAN is the default validator of lion-input-iban.

If consumers see the message like Please configure an error message for "IsIBAN" by overriding "static async getMessage()", it is easier to figure out what needs to be done.

Also this behavior is more consistent with how other validators work and its document: https://lion-web.netlify.app/components/input-iban/use-cases/#country-restrictions

To get the default feedback message for this default validator, use loadDefaultFeedbackMessages from @lion/form-core.

Discussion

• Even with the given benefits, whether they are worth the breaking change is a separate issue
• Is this technically a breaking change, while the new behavior is conforming to the existing document?

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4c02297

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[CLAassistant]

All committers have signed the CLA.