Add custom prev-next option

[kprosise]

Checks page for prev_link/next_link and prev_title/next_title first, to allow for custom prev/next links. This also allow for custom titles, which, while not yet utilized, can be useful in situations such as shortening a long page title's link.

Enabled on two pages, to address issue with container only path leading to an LmP content page, and for fioctl to point back to getting started, rather than an LmP content page.

Checked running a local server instance for correct rendering and links.

This commit applies to issue FFTK-4720, "…Getting Started flow…" This commit applies to issue FFTK-4681, "…Customizable prev/next…"

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)
• Merge after date or event
• Draft

Checklist

• View HTML in a browser to check rendering.
• 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.

Comments

Any thing else that a maintainer/reviewer should know.
This could include potential issues, rational for approach, etc.

[kprosise]

I will add the analytics stuff in sometime in the near future, keeping it out to make it easier to review just this fix.

[vanmaegima]

LGTM
Working as expected!

[mike-scott]

Thanks @kprosise -- this was exactly what we needed.