Declaring dependency on drupal/field in composer causes circular dependency on non-existent package

Problem/Motivation

Explicitely declaring a dependency in composer.json on the core field module creates a situation where you can no longer update drupal core:

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - drupal/email_formatter is locked to version 2.0.0-rc1 and an update of this package was not requested.
    - drupal/core-recommended 9.4.5 requires drupal/core 9.4.5 -> satisfiable by drupal/core[9.4.5].
    - Conclusion: don't install drupal/core 9.4.5 (conflict analysis result)
    - drupal/core-recommended 9.5.x-dev requires drupal/core 9.5.x-dev -> satisfiable by drupal/core[9.5.x-dev].
    - Conclusion: don't install drupal/core 9.5.x-dev (conflict analysis result)
    - drupal/email_formatter 2.0.0-rc1 requires drupal/field * -> satisfiable by drupal/core[8.0.0-beta6, ..., 8.9.x-dev, 9.0.0-alpha1, ..., 9.4.3, 10.0.0-alpha1, ..., 10.1.x-dev].
    - You can only install one version of a package, so only one of these can be installed: drupal/core[9.3.0-alpha1, ..., 9.5.x-dev].
    - drupal/core-recommended 9.4.x-dev requires drupal/core 9.4.x-dev -> satisfiable by drupal/core[9.4.x-dev].
    - Root composer.json requires drupal/core-recommended ^9.4 -> satisfiable by drupal/core-recommended[9.4.5, 9.4.x-dev, 9.5.x-dev].

Steps to reproduce

1. Update drupal/email_formatter to 2.0@RC
2. Attempt to update Drupal core to 9.4.5

Proposed resolution

Per Drupal best practices, remove the explicit dependency on "drupal/field" from the composer.json file to resolve this issue.