Add path to Keystore

[rootulp]

What type of PR is this?

Bug fix

What does this PR do? Why is it needed?

Adds path to the Keystore struct because it is a required JSON field per EIP-2335

Which issues(s) does this PR fix?

Fixes #10107

[CLAassistant]

All committers have signed the CLA.

[rootulp]

Thanks for the feedback @rkapka. I addressed so this PR is ready for re-review.

[james-prysm]

looks like you need to run the gazelle prefix "github.com/prysmaticlabs/prysm/validator/keymanager" command in the validators keymanager folder to fix the linter, must be from added dependencies for test. thanks for the contribution LGTM after that.

[rootulp]

Thanks for the tip @james-prysm !

On a slightly related note, brew install bazel installs bazel 5.0.0 and it looks like this project is using 4.2.2 per

prysm/.bazelversion

Line 1 in 4b3a723

4.2.2

Should I open a new issue to track upgrading to bazel 5.0.0 because it doesn't look like such an issue exists yet (search).

[james-prysm]

Thanks for the tip @james-prysm !

On a slightly related note, brew install bazel installs bazel 5.0.0 and it looks like this project is using 4.2.2 per

prysm/.bazelversion

Line 1 in 4b3a723

4.2.2

Should I open a new issue to track upgrading to bazel 5.0.0 because it doesn't look like such an issue exists yet (search).

let me double check with the team I'm sure they know about bazel 5.0.0 but might not be ready to upgrade yet ( assumption) i'd hold off on it. happy to continue the conversation on discord if interested.

[rootulp]

Sounds good, I'll hold off on creating a GH issue.

[rkapka]

This PR should definitely not update Bazel.

[james-prysm]

will test out UI with this change so see backwards compatability before merging

[james-prysm]

Approving this PR after testing out the following

1. backup account returns a keystore with path property
2. import keystore with new path property still works
3. import keystore without new path property still works
4. backup keystore without new path property returns a keystore with path property

[rootulp]

This PR should definitely not update Bazel.

Agreed. My intention was to create a separate GH issue to track upgrading to Bazel 5.0.0 but defer to you / the rest of the maintainers on how best to track that effort.

Thanks for reviewing and merging! Keep up the great work on Prysm.