DaplaUserInfoMapper replace TeamsMapper

[kschulst]

Support for retrieving user, group and team info from Dapla Team API. Replaces the TeamsMapper.

Produces JSON claims, such as:

{
    "teams" : [ {
      "uniform_name" : "dapla-felles",
      "section_code" : "724",
      "autonomy_level" : "SELF_MANAGED",
      "source_data_classification" : [ ],
      "groups" : [ ]
    }, {
      "uniform_name" : "mus-ost",
      "section_code" : "399",
      "autonomy_level" : "SELF_MANAGED",
      "source_data_classification" : [ "PII", "CONSENT_BASED" ],
      "groups" : [ "developers" ]
    }, {
      "uniform_name" : "play-foeniks-a",
      "section_code" : "724",
      "autonomy_level" : "SELF_MANAGED",
      "source_data_classification" : [ ],
      "groups" : [ "developers", "data-admins", "consumers", "editors" ]
    } ],
    "section_code" : "399"
}

or (flat/non-nested)

{
  "teams" : [ "dapla-felles", "mus-ost", "play-foeniks-a" ],
  "groups" : [ "mus-ost-developers", "play-foeniks-a-developers", "play-foeniks-a-data-admins", "play-foeniks-a-consumers", "play-foeniks-a-editors" ]
}

Team and user properties to include are configurable. In addition, groups can be filtered by matching against a configurable regex, e.g. if you only want to include certain dapla groups such as developers. In that case, it is also configurable whether you want to only have teams with relevant groups or if all teams should be included.

Screenshot from the Keycloak Admin GUI:

This PR also adds a localstack setup that uses docker-compose to provide a local Keycloak instance that can be used for local development. It is very handy, essential even, to test the protocol mapper against a real Keycloak server.