Add example to string-decode and update documentation "how to publish" flux-commands.md

[dr0i]

• update documentation "how to publish" flux-commands.md

Complements #54.

[TobiasNx]

The docupage used to be a list of the current released flux commands. If we change this to the master status how can we highlight that a command is not available yet on the release.

[dr0i]

But i's also a problem to have mf-core-master not in sync with mf-documentation. E.g. our playground uses the mf-core-master, thus a mf-pg user would find commands in the pg which are not documented.
I don't know, we could add a tag of the release on the documentation to show where the documentation is in sync with mf-core ?

[TobiasNx]

I agree with tagging. We also would have to adjust our workflow by updating the docu page with every merge of core into the master.

[TobiasNx]

I tried to capture the current problem with the documentation process in a new ticket: #59

[TobiasNx]

We discussed this PR was troubled with miscommunication next time I should make my wishes for changes explicit (two different changes in one commit) also I should have assinged @dr0i when I have a question.