Setup workflow for publishing dev version

[kprosise]

Note that this is a draft/first-go at publishing both a dev version of the docs, and publishing via a GitHub workflow. This will likely require additional work. Workflow was kept simple and set to handle a single case—publish when a commit is merged to next branch of the docs.

QA steps: Ran actionlint on the workflow file, which produced a couple warnings: possible globbing issue due to expression used for getting the fioctl version, and a possible side effect for one of the assignments.

This commit applies to issue FFTK-4532, "Add dev version" This commit applies to issue FFTK-4116, "…GitHub action for publishing"

PR Template and Checklist

Please complete as much as possible to speed up the reviewing process.
You may delete items that are not relevant to your contribution.
Readiness and adding reviewers as appropriate is required.

All PRs should be reviewed by a technical writer/documentation team and a peer.
If effecting customers—which is a majority of content changes—a member of Customer Success must also review.

Readiness

• Merge (pending reviews)
• Draft

Checklist

• follow best practices for commits.
  • Descriptive title written in the imperative.
  • Include brief overview of QA steps taken.
  • Mention any related issues numbers.
  • End message with sign off/DCO line (-s, --signoff).
  • Sign commit with your gpg key (-S, --gpg-sign).
  • Squash commits if needed.
• Request PR review by a technical writer and at least one peer.

[kprosise]

@doanac Regarding the final steps of uploading the docs, I just want to make sure I am not missing anything or doing anything that will, you know, cause a problem like accidently deleting all of the docs…again. If you don't see any glaring issues, I can merge and begin working out any issues.

[doanac]

this looks sane.