Recognize the availability of a valid later module release which is not backwards compatible

Problem/Motivation

Some drupal modules have a Drupal 10 compatible release which is not compatible with Drupal 9.
Geocoder users struggled with this for some time but were eventually led to csv_serialization which had a solution:
See: https://www.drupal.org/project/geocoder/issues/3283651#comment-15050664 ✨ Drupal 10 compatibility: changing php-http/guzzle6-adapter dependency into php-http/guzzle7-adapter RTBC
The solution requires a manual change to composer.json to expand the version requirements to, in this case,

"require": {
  ...
  "drupal/geocoder": "^3.20 || ^4.0",
  ...
}

This could be achieved within upgrade_status, although I don't have the capablity to implement a suitable solution.

Steps to reproduce

Upgrade status reports that geocoder, in this case, is incompatible. But after expanding the version requirment manually as above the upgrade script worked successfully:
composer require 'drupal/core-recommended:^10' 'drupal/core-composer-scaffold:^10' 'drupal/core-project-message:^10' --update-with-dependencies --no-update
Followed by:
composer update
Database updates proceeded correctly.

Drupal updated to 10.0.9 and geocoder updated to 8.x-4.9.

Success.

Proposed resolution

Add the capability to the code.