Retooling pbench-move-results to use the RESTful PUT API instead of direct ssh

[riya-17]

This PR mainly deals with using RESTful PUT API instead of ssh for sending Tarballs from agent to server. At the time of sending of tarballs, it consists of an Authorization token (generated with the help of pbench-generate-token command)which will help for authorizing the owner of the Tarballs.

It uses 'click' for the creation of a command-line interface.
Also consists of config file changes and pytests.

Sorting of the config files is taken care in PR #2190

[webbnh]

Looks like a good start, but there is a bunch of polishing which needs to be done.

[lgtm-com]

This pull request introduces 1 alert when merging e596c34 into dc48a16 - view on LGTM.com

new alerts:

• 1 for Unused exception object

[lgtm-com]

This pull request introduces 1 alert when merging 3147ee0 into ea02995 - view on LGTM.com

new alerts:

• 1 for Unreachable code

[portante]

Looking good; just want to avoid introducing a new way of handling imports without agreeing on it (see #2238).

[ndokos]

LGTM

[webbnh]

Reordered the import's and rebased on main.

[webbnh]

Functional testing, such as it was, is complete. (The server says it's good, unless I upload the same file twice, in which case the tool reports the server's objection.)

So, if I can get the nod from @portante and one other person, this PR is good to squash-and-merge.

[portante]

Ship it!

[dbutenhof]

Leaving the big question of whether Pete wants the 12 commits squashed before hitting the Squash and merge button?

[portante]

Not sure why, but it needs a rebase, so might as well rebase and squash it to one commit.

[webbnh]

Leaving the big question of whether Pete wants the 12 commits squashed before hitting the Squash and merge button?

I want that button to be useful! (And, I want to avoid the re-approval cycle between the approval and the merge which externally squashing requires.) I wanted to try it to see if it really doesn't work acceptably....

As long as I'm griping, I resent the "Update Branch" button: if I'm going to rebase my branch, then I certainly don't want the outstanding commits from main merged into it! That button should have a pull-down like the merge button does which offers the alternative of rebasing. (And, given that our repository has merge commits disabled, the "update" button shouldn't even offer the option of merging!)

Not sure why, but it needs a rebase, so might as well rebase and squash it to one commit.

Ha! 'Cause somebody merged two PRs since I last rebased -- that's why! :-D

Anyway, the squash is done, and I'm just prattling on here while I wait for the checks to run....