test(cli): warp commands e2e tests

[xeno097]

Description

This PR tries to e2e test multiple use cases with warp commands to ensure that future changes that might break or change the commands' behavior are detected early.

Drive-by changes

• fixes skipConfirmation propagation in signer strategy code
• move the warp e2e tests into the test/warp folder

Related issues

• Better e2e test in the CLI #5080

Backward compatibility

• YES

Testing

• Manual
• E2E

[changeset-bot]

⚠️ No Changeset found

Latest commit: 019d8d2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 77.53%. Comparing base (9574b1b) to head (019d8d2).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5121   +/-   ##
=======================================
  Coverage   77.53%   77.53%           
=======================================
  Files         103      103           
  Lines        2110     2110           
  Branches      190      190           
=======================================
  Hits         1636     1636           
  Misses        453      453           
  Partials       21       21           

Components	Coverage Δ
core	87.80% <ø> (ø)
hooks	79.39% <ø> (ø)
isms	83.68% <ø> (ø)
token	91.27% <ø> (ø)
middlewares	79.80% <ø> (ø)

[jmrossy]

the createWarpRouteConfigId and BaseRegistry.getWarpRoutesPath functions in the registry package can help you reduce duplication with Registry code here

[xeno097]

I haven't reused the BaseRegistry.getWarpRoutesPath because it is marked as protected. Thanks for the createWarpRouteConfigId suggestion 🔥