views.view.redirect.yml and views.view.redirect_404.yml do not match Drupal's export

MR Added.

No brainer.

As per the issue description and gitlab pipeline failure for previous minor i.e D10.2.x ~~ I would strongly suggest to cut new major branch with minimum support of D10.3

cc: @berdir

I don't really see the need for a new branch. 10.2 is already dropped from active support and will drop security support in a few months.

I'm not really willing to drop last minor testing, and even less so to to create a major new release because of a single new optional config key.

I understand what recipe API is trying to do, but this feels like a adding quite some burden on maintainers just because core decides to add a new feature. What's redirect supposed to do when views adds another such key in the next minor? and another in the next? Release new minor/major versions every time that then need to be maintained?

Maybe config schema should include a default value system, and missing values that match the default could be ignored somehow? Just thinking out loud.

Updating to add the view file in the Redirect 404 submodule.

While the tests fail, has anyone tested manually installing this change on a 10.2 site? I feel like this should be something that core handles better.