Add min hops manipulation endpoint

[alexadhy]

Did you run make format && make check? yes

Fixes #770

Related to:

• Add router related config to the manager #729

Changes:

• Added min_hops endpoint to the http API and rpc one (@jdknives @Senyoret1 not sure about the latter, since there's route-finder)

How to test this PR:

• run it in the integration test (using v111 config)
• do an http call to the /visors/{pk}/min-hops endpoint (POST and GET) like:

$ curl -k https://localhost:8000/api/visors/${PK}/min-hops
$ curl -k -d '{"min_hops": 1}' -H "Content-Type: application/json" -X POST  https://localhost:8000/api/visors/${PK}/min-hops

• or do an rpc call via skywire-cli visor route get-min-hops and skywire-cli visor route set-min-hops <some_number>

[jdknives]

Not sure if we should add the CLI commands just to be consistent. I cant see a use for it effectively so we may get rid of it. But also does not hurt to have it.

[Senyoret1]

I have 2 comments about the implementation:

• It would be good if the GET /api/visors/{pk}/summary API endpoint returns the data, that way the UI would not have to make an additional API call, which would make the UI a bit slower.
• Is there also a max hops configuration? If that is the case, it sould be added to the API too.

[alexadhy]

@Senyoret1:

• first point makes sense, done.
• currently there's no max hops configuration

[Senyoret1]

Great, I implemented the changes in #729, thanks 👍