MCR-3639 Add support for annotation based configuration of string-valued maps and lists

[toKrause]

Link to jira.

Pull Request Checklist (Author)

Please go through the following checklist before assigning the PR for review:

Ticket & Documentation

• The issue in the ticket is clearly described and the solution is documented.
• Design decisions (if any) are explained.
• The ticket references the correct source and target branches.
• The fixed-version is correctly set in the ticket and matches the PR's target branch (main).

Feature & Improvement Specific Checks

• Instructions on how to test or use the feature are included or linked (e.g. to documentation).
• For UI changes: before & after screenshots are attached.
• New features or migrations are documented.
• Does this change affect existing applications, data, or configurations?
  • Yes: Is a migration required? If yes, describe it.
  • Breaking change is marked in the commit message.

Testing

• I have tested the changes locally.
• The feature behaves as described in the ticket.
• Were existing tests modified?
  • Yes: explain the changes for reviewers.

As per Scout rule: Test property names and values used in MCRConfigurableInstanceHelperNestedTest have been changed to align with the new test class MCRConfigurableInstanceHelperCollectionTest which has similar tests (the names and values have become a bit unwieldy). List#getFirst() has been replaced with List#get(0) in the tests, b/c it better reflects the indexed-based access to the tested lists.

MCR Conventions & Metadata

• MCR naming conventions are followed
• If the public API has changed:
  • Old API is deprecated or a migration is documented.
  • If not, no action needed.
• Java license headers are added where necessary.
• Javadoc is written for non-self-explanatory classes/methods (Clean Code).
• All configuration options are documented in Javadoc and mycore.properties.
• No default properties are hardcoded — all set via mycore.properties.

Multi-Repo Considerations

• Is an equivalent PR in MIR required?
  • If yes, is it already created?

[sebhofmann]

Some fixes required.

[sebhofmann]

This will throw a "cryptic" message if they keys are no integer. Maybe throw a better error like:

  propertyMap.forEach((key, value) -> {
      try {
          orderedPropertyMap.put(Integer.parseInt(key), value);
      } catch (NumberFormatException e) {
          throw new MCRConfigurationException(
              "Property list key '" + prefix + key + "' is not a valid integer index", e);
      }
  });

[toKrause]

This is being done as part of #2861

[sebhofmann]

This should maybe print a warning if there are some wrong mappings without :

  private Map<String, String> parseShortFormMap(String value) {
      return MCRConfiguration2.splitValue(value)
          .map(s -> s.split(":", 2))
          .filter(parts -> {
              if (parts.length == 1) {
                  LOGGER.warn("Ignoring short form map entry '{}' - missing ':' separator", parts[0]);
                  return false;
              }
              return true;
          })
          .filter(parts -> !parts[1].isBlank())
          .collect(Collectors.toMap(parts -> parts[0].trim(), parts -> parts[1].trim()));
  }

[toKrause]

Some fixes required.

Thx for the feedback. Issues should be fixed now.