[PP-1] Add validation constraints to claro.settings

Problem/Motivation

Claro's settings have 1 property paths that are not yet validatable:

$ ./vendor/bin/drush config:inspect --filter-keys=claro.settings --detail --list-constraints  --fields=key,validatability,constraints➜  🤖 Analyzing…

 ----------------------------------------------------------- ------------- ------------------------------------------ 
  Key                                                         Validatable   Validation constraints                    
 ----------------------------------------------------------- ------------- ------------------------------------------ 
  claro.settings                                              75%           ValidKeys: '<infer>'                      
                                                                            RequiredKeys: '<infer>'                   
   claro.settings:                                            Validatable   ValidKeys: '<infer>'                      
                                                                            RequiredKeys: '<infer>'                   
   claro.settings:third_party_settings                        NOT           ⚠️  @todo Add validation constraints here  
   claro.settings:third_party_settings.shortcut               Validatable   ValidKeys: '<infer>'                      
                                                                            RequiredKeys: '<infer>'                   
   claro.settings:third_party_settings.shortcut.module_link   Validatable   ↣ PrimitiveType: {  }                     
 ----------------------------------------------------------- ------------- ------------------------------------------ 

Steps to reproduce

1. Get a local git clone of Drupal core 11.x.
2. composer require drupal/config_inspector — or manually install https://www.drupal.org/project/config_inspector/releases/2.1.5 or newer (which supports Drupal 11!)
3. composer require drush/drush
4. vendor/bin/drush config:inspect --filter-keys=olivero.settings --detail --list-constraints

Proposed resolution

Add validation constraints to:

1. third_party_settings

This requires looking at the existing code and admin UI (if any) to understand which values could be considered valid. Eventually this needs to be reviewed by the relevant subsystem maintainer.

For examples, search *.schema.yml files for the string constraints: 😊

Reach out to @borisson_ or @wimleers in the #distributions-and-recipes.

Remaining tasks

1. third_party_settings

User interface changes

None.

API changes

None.

Data model changes

More validation 🚀

Release notes snippet

None.