Ledger derivation path not accepting initial m/ as valid

[JagoFigueroa]

Describe the bug
While testing the feature for custom derivation paths on ledger we noticed that the initial m/ of the path is not accepted as a valid argument.

To Reproduce
Access a safe from the cli with the ledger connected and try the following commands:

blockchain > 0x6D04edC44F7C88faa670683036edC2F6FC10b86e > load_ledger_cli_owners --derivation-path m/44'/60'/0'/0/0
HwDevice exception: The provided derivation path is not valid
blockchain > 0x6D04edC44F7C88faa670683036edC2F6FC10b86e > load_ledger_cli_owners --derivation-path m'/44'/60'/0'/0/0
HwDevice exception: The provided derivation path is not valid
blockchain > 0x6D04edC44F7C88faa670683036edC2F6FC10b86e > load_ledger_cli_owners --derivation-path 44'/60'/0'/0/0
Loaded account 0x454a478d2482C1d251F149424053d4485aDD3dC5 with balance=0.044340226882541042 ether.
Ledger account cannot be defined as sender

Current behavior
load_ledger_cli_owners --derivation-path m/44'/60'/0'/0/0 not valid

Expected behavior
load_ledger_cli_owners --derivation-path m/44'/60'/0'/0/0 should be valid