docs(fioctl): add examples of tags and apps

[StealthyCoder]

PR Template and Checklist

Please complete as much as possible to speed up the reviewing process.

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

Overview

This PR adds some examples for the fioctl commands surrounding tags and apps, which have some specific logic, that was not previously documented other than in the code and maybe in the help of the command itself.

Checklist

• Run spelling and grammar check, preferably with linter.
• Avoid changing any header associated with a link/reference.
• Step through instructions (or ask someone to do so).
• Review for wordiness
• Match tone and style of page/section.
• Run make linkcheck.
• View HTML in a browser to check rendering.
• Use semantic newlines.
• 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

[kprosise]

LGTM! Squash/fixup and then I would be happy to merge! Thanks for the additional fixes!

[StealthyCoder]

@kprosise I squashed them into 4, let me know if you think that is enough or you want them more compressed. 💪