Multiple dependency versions causing yarn dependency warning [Bug?]

[seanblonien]

Expected behaviour: No yarn warnings when there are multiple version of the same package
Actual behaviour: Yarn install warnings incorrectly warn about a missing peer dependency that is provided

reproduction in yarn v3 playground

const {promises: {readFile}} = require(`fs`);

const output = await packageJsonAndInstall({
  dependencies: {
    [`@backstage/plugin-scaffolder`]: `^1.12.0`
  }
});
console.log(output);

/**
 * lockfile contains these dependencies with this tree:
 *   @backstage/plugin-scaffolder -> @backstage/plugin-scaffolder-react  -> @rjsf/core-v5@npm:@rjsf/[email protected]
 *   @backstage/plugin-scaffolder -> @backstage/plugin-scaffolder-react  -> @rjsf/core@^3.2.1
 *   @backstage/plugin-scaffolder -> @backstage/plugin-scaffolder-react  -> @rjsf/material-ui@^3.2.1  ->  @rjsf/core@^3.2.1
 *   @backstage/plugin-scaffolder -> @backstage/plugin-scaffolder-react  -> @rjsf/material-ui-v5@npm:@rjsf/[email protected]  ->  @rjsf/core@^5.0.0
 */
const lockfile = await readFile(`yarn.lock`, `utf8`);
expect(lockfile).toContain(`@rjsf/material-ui-v5`);

// How do we tell yarn that we *do* satisfy peer requirements? 
// Is it possible for two libraries of different dependency resolutions to refer to the same package by name?
// How does yarn suggest we name dependencies of different versions and resolve specific sub-depndencies to a slightly different named package?
const explain = await yarn(`explain`, `peer-requirements`, `p64975`);
expect(explain).not.toContain(`provides @rjsf/core`);

Creating this discussion directly out of this: backstage/backstage#16982

This @backstage project has the need to support two different versions of @rjsf/material-ui, and has tried to rename the dependencies with -v5 resolving to compatible v5 versions, but yarn can't recognize the different version because internally the @rjsf/material-ui and @rjsf/material-ui-v5 dependencies refer to the same name of @rjsf/core which only resolves to one version (3.2.1 in this case) causing the warning

How do we tell yarn in the original package.json file of one of these @backstage packages how to resolve the ambiguous @rjsf/core?

Or, if there is nothing that can be done for the package.json file of the package in the first place, how could we use .yarnrc.yml's packageExtensions property to force resolve?

This .yarnrc.yml configuration did not make the warning go away:

nmMode: classic
nodeLinker: node-modules

yarnPath: .yarn/releases/yarn-3.5.0.cjs

packageExtensions:
  '@rjsf/material-ui@*':
    dependencies:
      '@rjsf/core': '^3.2.1'
  '@rjsf/material-ui-v5@*':
    dependencies:
      '@rjsf/core': '^5.1.0'

yarn install warning:

➤ YN0060: │ @backstage/plugin-scaffolder-react@npm:1.2.0 [59280] provides @rjsf/core (pd44c4) with version 3.2.1, which doesn't satisfy what @rjsf/material-ui requests
...
➤ YN0000: ┌ Post-resolution validation
➤ YN0068: │ @rjsf/material-ui-v5 ➤ dependencies ➤ @rjsf/core: No matching package in the dependency tree; you may not need this rule anymore.

@arcanis tagging a maintainer for visibility