Bump Plutus deps to 1.11

[bezirg]

Description

Checklist

• Commit sequence broadly makes sense and commits have useful messages
• New tests are added if needed and existing tests are updated
• When applicable, versions are updated in .cabal and CHANGELOG.md files according to the
  versioning process.
• The version bounds in .cabal files for all affected packages are updated. If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)
• All visible changes are prepended to the latest section of a CHANGELOG.md for the affected packages. New section is never added with the code changes. (See RELEASING.md)
• Code is formatted with fourmolu (use scripts/fourmolize.sh)
• Cabal files are formatted (use scripts/cabal-format.sh)
• hie.yaml has been updated (use scripts/gen-hie.sh)
• Self-reviewed the diff

[lehins]

Whenever bounds in a cabal file are changed the patch version of the package needs to be increased, otherwise the package will not get released next time we'll be going through a release process. So, could you please bump the last number in versions for these packages:

• cardano-ledger-alonzo-test
• cardano-ledger-binary

[lehins]

This will break some of the plutus functionality in Conway, but the breakage only affects Conway and PlutusV3, so this is totally fine