feature(peridot-cli): add task logs command

[NeilHanlon]

feature(peridot-cli): add task logs command

peridot task logs will accept either a build ID or package name. In
the latter case, the project will be queried for the latest build for
the given package name. With the build task ID in hand, the task can be
queried for its BUILD_ARCH subtasks, which contain the logs for the
binary RPM builds.

Passing -C or --cwd with a directory will change into that directory
before writing files. That directory must exist beforehand.
Otherwise, $PWD is used.

By default, a separate file will be created for each
$taskId-$subtaskId-$architecture tuple, which accounts for modular packages
with multiple outputs.

Passing the -c or --combined flag will combine all the logs into a
single file, named $taskId.log

[resf-prow]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[NeilHanlon]

• feat(peridot-cli/task-info): fetch and display task details #196
• feature(peridot-cli): add task logs command  #195 👈 (View in Graphite)
• feat/build-peridot-cli-rpm

This stack of pull requests is managed by Graphite. Learn more about stacking.

[MatthewHink]

Thank you!

[resf-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: MatthewHink, NeilHanlon

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [NeilHanlon]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment