feat(rust): delete relays interactive

[PanGan21]

Current behavior

Errors out when the user doesn't specify a relay name.

Proposed changes

Closes #6464

• relay_name argument becomes optional
• If the user provides a relay_name then uses the provided relay_name
• If the user doesn't provide a relay_name and the terminal is interactive, and the user didn't pass any of --no-output or --quiet flags then the terminal shows all available relays and allows the user select one or more from a list
• Then for all the selected relays - one for old case - multiple or one for new case - check, confirm and delete

Checks

• All commits in this Pull Request are signed and Verified by Github.
• All commits in this Pull Request follow the Ockam commit message convention.
• There are no Merge commits in this Pull Request. Ockam repo maintains a linear commit history. We merge Pull Requests by rebasing them onto the develop branch. Rebasing to the latest develop branch and force pushing to your Pull Request branch is okay.
• I have read and accept the Ockam Community Code of Conduct.
• I have read and accepted the Ockam Contributor License Agreement by adding my Git/Github details in a row at the end of the CONTRIBUTORS.csv file in a separate pull request to the build-trust/ockam repository. The easiest way to do this is to edit the CONTRIBUTORS.csv file in the github web UI and create a separate Pull Request, this will mark the commit as verified.

[mrinalwadhwa]

@PanGan21 Thank you for spending time on this, before we can merge please

• Accept the Ockam Contributor License Agreement by adding your Git/Github details in a row at the end of the CONTRIBUTORS.csv file in a separate new pull request to the build-trust/ockam repository.

The easiest way to do this is to edit the CONTRIBUTORS.csv file in the github web UI and create a PR, this will mark the commit as verified.

[PanGan21]

@PanGan21 Thank you for spending time on this, before we can merge please

• Accept the Ockam Contributor License Agreement by adding your Git/Github details in a row at the end of the CONTRIBUTORS.csv file in a separate new pull request to the build-trust/ockam repository.

The easiest way to do this is to edit the CONTRIBUTORS.csv file in the github web UI and create a PR, this will mark the commit as verified.

Hi @mrinalwadhwa ! Thanks for the reminder. Is it required to be done in a separate pr or I can just push the new CONTRIBUTORS.csv in this pr?

[mrinalwadhwa]

@PanGan21 in a separate PR please

[PanGan21]

@PanGan21 in a separate PR please

Done in this pr #6744

[PanGan21]

Hi @mrinalwadhwa would it be possible to review this pr in October?

[adrianbenavides]

Hey @PanGan21 thanks for the PR! We are refactoring several commands to add the tui experience. You should use the node delete logic as a reference and keep the code as similar to that as possible.

Here is the code:

ockam/implementations/rust/ockam/ockam_command/src/node/delete.rs

Line 44 in 2a2843e

fn run_impl(opts: CommandGlobalOpts, cmd: DeleteCommand) -> miette::Result<()> {

[mrinalwadhwa]

@PanGan21 while we still have to review this change. I'm adding the HACKTOBERFEST-ACCEPTED label so the contribution is counted by hacktoberfest bots before the end of October. Thank you for taking time to contribute 🎉

Please not @adrianbenavides's comment above.

[PanGan21]

Hey @PanGan21 thanks for the PR! We are refactoring several commands to add the tui experience. You should use the node delete logic as a reference and keep the code as similar to that as possible.

Here is the code:

ockam/implementations/rust/ockam/ockam_command/src/node/delete.rs

Line 44 in 2a2843e

fn run_impl(opts: CommandGlobalOpts, cmd: DeleteCommand) -> miette::Result<()> {

Hi! I did some refactoring, let me know what you think

[adrianbenavides]

@PanGan21 Your PR is going to be merged as part of #6889. You'll appear as co-author of the PR's commit 👍 Thank you so much for your help with this one 🙏