PrimitiveTypeConstraintValidator vs ConfigSchemaChecker: test coverage to establish the status quo

Did not test but seems there is a failing kernel test.

smustgrave → credited phenaproxima → .

Crediting phenaproxima for the reviews on the MR.

So the feedback appears addressed but will leave for @phenaproxima to take another look.

Looks pretty good but leaving at NR because I'm still not sure some of the commentary is as clear as it could/should be.

I think the comments are pretty good; in my opinion this is good to go.

It's really different to be triggering deprecations in a test and then adding generic ignores. This feels wrong and very odd. I'm not really sure what we're communicating here.

@alexpott did you see:

# Temporarily while updating PrimitiveTypeConstraintValidator and ConfigSchemaChecker to agree with each other.
# @todo Remove in https://www.drupal.org/project/drupal/issues/3230826.
%The `type: (string|boolean|float|int)` config schema type uses magical casting when saving.%
%⚠️ The `type: boolean` config schema type uses magical casting for the string value `(no|test|false|)` that is inconsistent with the validation logic in Drupal\\Core\\Validation\\Plugin\\Validation\\Constraint\\PrimitiveTypeConstraintValidator.%
%⚠️ The `type: (int|float)` config schema type uses magical casting for the string value `(55\%|)` that is inconsistent with the validation logic in Drupal\\Core\\Validation\\Plugin\\Validation\\Constraint\\PrimitiveTypeConstraintValidator.%
%⚠️ The `type: (int|float)` config schema type uses magical casting for the boolean value `` that is inconsistent with the validation logic in Drupal\\Core\\Validation\\Plugin\\Validation\\Constraint\\PrimitiveTypeConstraintValidator.%

?

The reason this MR is adding generic ignores is to allow this issue to be tightly scoped to ONLY documenting the current behavior in explicit tests. That then enables 📌 Expose API to sort arbitrary config arrays Needs work to remove the magic (i.e. not just documenting current behavior, but making it consistent), modify the expectations of the tests added here, and remove the generic ignores.

The generic ignores do not negatively impact anyone? But they do allow this pure-test-coverage issue to help unblock the much more complex 📌 Expose API to sort arbitrary config arrays Needs work 😇

The Needs Review Queue Bot → tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".

This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.

Consult the Drupal Contributor Guide → to find step-by-step guides for working with issues.

Just noting that #2142995 might have some overlap here?