relay-cli: Handle None case for shared base path

[cdamian]

Description

When running the centrifuge-chain locally, if no base-path is provided to the relay chain args then a random temp directory is used which can cause inconsistent behavior such as the chain not producing blocks due to invalid/stale data in the db.

Changes and Descriptions

The changes in this PR aim at handling the case where shared_params().base_path() is a Result(None) which results in the behavior described above.

Type of change

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Tested by running the chain locally and confirming that the base_path set in the init script is used for the relay chain.

Checklist:

• I have added Rust doc comments to structs, enums, traits and functions
• I have made corresponding changes to the documentation
• I have performed a self-review of my code
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I rebased on the latest main branch

[mustermeiszer]

Thanks for the quick fix!

cc: @mikiquantum the reason being is that we had a silent logic change on the Substrate side, where the cli implementation now provides temp paths automatically when running in dev mode and no path is provided to the relay-chain cli.

[mustermeiszer]

LGTM!