Forc-deploy import wallet support if non-existent wallet

[zees-dev]

Description

• Adds support for importing a wallet on forc-deploy
• Resolves Prompt user to enter seed phrase whenever we prompt them to create a new wallet forc-wallet#139

[sdankel]

The prompt about creating/importing a wallet should come before asking for the wallet password. Otherwise, once the tests are passing, LGTM 😃

[zees-dev]

The prompt about creating/importing a wallet should come before asking for the wallet password. Otherwise, once the tests are passing, LGTM 😃

The current behaviour performs the password check which is much more upstream in the code; changing that would imply a re-factor which may have knock-on effects.
I think this would be worthwhile addressing as a seperate issue.
If we have agreement; I can create an issue for that.

[kayagokalp]

The prompt about creating/importing a wallet should come before asking for the wallet password. Otherwise, once the tests are passing, LGTM 😃

The current behaviour performs the password check which is much more upstream in the code; changing that would imply a re-factor which may have knock-on effects. I think this would be worthwhile addressing as a seperate issue. If we have agreement; I can create an issue for that.

I think we should discuss the necessary refactor to do this, because it feels a little confusing as it is. If i don't have a wallet it is highly likely that I don't have necessary context to understand what password I need to enter once that is prompted. So it might be worth doing the refactor before merging this.

If you can come up with some kind of a description of what you need to be changed exactly I am more than happy to help out! I want to clean forc deploy paths for some time now even have a tracking issue for it. #6259

[zees-dev]

The prompt about creating/importing a wallet should come before asking for the wallet password. Otherwise, once the tests are passing, LGTM 😃

The current behaviour performs the password check which is much more upstream in the code; changing that would imply a re-factor which may have knock-on effects. I think this would be worthwhile addressing as a seperate issue. If we have agreement; I can create an issue for that.

I think we should discuss the necessary refactor to do this, because it feels a little confusing as it is. If i don't have a wallet it is highly likely that I don't have necessary context to understand what password I need to enter once that is prompted. So it might be worth doing the refactor before merging this.

If you can come up with some kind of a description of what you need to be changed exactly I am more than happy to help out! I want to clean forc deploy paths for some time now even have a tracking issue for it. #6259

I believe this should be done in another PR as the scope could become much larger.
In this PR we just want to give option for user to import seed phrase; without changing/refactoring the upstream flow.

[kayagokalp]

The prompt about creating/importing a wallet should come before asking for the wallet password. Otherwise, once the tests are passing, LGTM 😃

The current behaviour performs the password check which is much more upstream in the code; changing that would imply a re-factor which may have knock-on effects. I think this would be worthwhile addressing as a seperate issue. If we have agreement; I can create an issue for that.

I think we should discuss the necessary refactor to do this, because it feels a little confusing as it is. If i don't have a wallet it is highly likely that I don't have necessary context to understand what password I need to enter once that is prompted. So it might be worth doing the refactor before merging this.
If you can come up with some kind of a description of what you need to be changed exactly I am more than happy to help out! I want to clean forc deploy paths for some time now even have a tracking issue for it. #6259

I believe this should be done in another PR as the scope could become much larger. In this PR we just want to give option for user to import seed phrase; without changing/refactoring the upstream flow.

I don't think we should merge this as it is because as it is this will be confusing, my suggestion would be to keep this ready to go and first fix the upstream and after that using the already fixed upstream let's merge this PR.

I am curious about what needs to be changed to fix this issue and if i understood correctly those needs to be fixed in forc-wallet, right?

[kayagokalp]

It turns out this situation is present for creating a new wallet as well. I opened #6704, once merged it will also fix the problem we are having here. If we can merge that and rebase this one wallet password won't be prompted.

Changes have been made