[Bug?]: --ignore-engines should throw a warning, not an error

[darkbasic]

Self-service

• I'd be willing to implement a fix

Describe the bug

➤ YN0050: The --ignore-engines option is deprecated; engine checking isn't a core feature anymore

Some github workflows try to be compatible with both yarn1 and berry, passing duplicate options like --frozen-lockfile --immutable in order to stay compatible with both.
Unfortunately --ignore-engines throws an error on berry, while it should probably be treated as a warning like --frozen-lockfile.
Engines are ignored anyway on berry.

To reproduce

yarn install --ignore-engines
➤ YN0050: The --ignore-engines option is deprecated; engine checking isn't a core feature anymore

Environment

System:
    OS: Linux 6.6 Arch Linux
    CPU: (16) x64 AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics
  Binaries:
    Node: 18.18.0 - /tmp/xfs-6c1b0828/node
    Yarn: 4.0.0-rc.53 - /tmp/xfs-6c1b0828/yarn
    npm: 10.2.0 - /run/user/1000/fnm_multishells/97785_1697529429361/bin/npm
  npmPackages:
    jest: 29.7.0 => 29.7.0

Additional context