CLI Warp Checker should reference deploy/warpcore config sanely

[nambrot]

Current behavior:

• warp check reads deploy config from DEFAULT_WARP_ROUTE_DEPLOYMENT_CONFIG_PATH
• warp check can be configured to read warp deploy config with the --config/-i flag to a file path
• warp check reads warpcore config from specifying the --symbol flag and if a specific warpCore config couldn't be found, it will give an interactive wizard to pick it
• warp check can be configured to read warpcore config from the --warp/-wc flag to a file path

Expected behavior:

• warp check can be configured with a --warpRouteId flag to find both the warpdeploy config (now in the configured registry due to Warp Deploy Config fetching and writing via IRegistry #5237) and the warpcoreconfig
• when not specified, an interactive wizard should give me the options of all warp route Ids in the specified warp registry. I should be able to use typeahead search to find the warp route that I want
• individual file paths to --config/-i for warp deploy config and --warp/-wc should still apply, however both have to be given together

Drive-by change:

• When a completely different warp deploy config (lets say involving chains A and B) is matched with a completely different warpcore config (lets say involving chains C and D), the diff should clearly state: expected: A, B, actual: C, D. Right now it just states expected A, B

[nambrot]

@mshojaei-txfusion this should be assinged to you and is in review yeah?