doc: redistributing: use latest tag for Golioth

[szczys]

Updated the links to the Golioth Zephyr SDK to use the latest v0.13.1 release.

This is a new PR that implements the same changes that were approved in #12551 (the difference is the version numbers have been updated to latest).

That PR was approved more than once but never merged. If there is anything I can do to help get this across the finish line, please let me know.

Approvers of the previous PR:

• @gregersrygg
• @nordicjm
• @peknis
• @wiba-nordic

[NordicBuilder]

Thank you for your contribution!
It seems you are not a member of the nrfconnect GitHub organization. External contributions are handled as follows:
Large contributions, affecting multiple subsystems for example, may be rejected if they are complex, may introduce regressions due to lack of test coverage, or if they are not consistent with the architecture of nRF Connect SDK.
PRs will be run in our continuous integration (CI) test system.
If CI passes, PRs will be tagged for review and merged on successful completion of review. You may be asked to make some modifications to your contribution during review.
If CI fails, PRs may be rejected or may be tagged for review and rework.
PRs that become outdated due to other changes in the repository may be rejected or rework requested.
External contributions will be prioritized for review based on the relevance to current development efforts in nRF Connect SDK. Bug fix PRs will be prioritized.
You may raise issues or ask for help from our Technical Support team by visiting https://devzone.nordicsemi.com/.

Note: This comment is automatically posted and updated by the Contribs GitHub Action.

[lemrey]

Thank you, I let CI run and added the milestone.

[NordicBuilder]

You can find the documentation preview for this PR at this link. It will be updated about 10 minutes after the documentation build succeeds.

Note: This comment is automatically posted by the Documentation Publishing GitHub Action.

[anangl]

This is a documentation change only, it does not need a CI run (the documentation build was successful).