Update Go Guide

[akeller]

Description

Closes #773.

When should this change go live?

• This change is not yet live and should not be merged until {ADD_DATE} (apply hold label or convert to draft PR)?
• There is no urgency with this change.
• This change or page is part of a marketing blog, conference talk, or something else on a schedule.
• This functionality is already available but undocumented.
• This is a bug fix or security concern.

PR Checklist

• I have added changes to the relevant /versioned_docs directory, or they are not for an already released version.
• I have added changes to the main /docs directory (aka /next/), or they are not for future versions.
• My changes require an Engineering review, and I've assigned an engineering manager or tech lead as a reviewer, or my changes do not require an Engineering review.
• My changes require a technical writer review, and I've assigned @christinaausley as a reviewer, or my changes do not require a technical writer review.

[akeller]

I need a Go expert to let me know if we should bump up the minimum version in the pre-requisites.

[akeller]

@megglos I added you, but feel free to delegate to a Zeebe/Go expert.

Most of the changes I made were incorporating both Modeler experiences and deploying your model from a file on your desktop programmatically or by clicking the deploy button in Web Modeler.

[akeller]

Added @Sijoma for his Go expertise, but he's on leave right now. (Also, stay on leave, this is not urgent!)

[megglos]

Hey @abbasadel given you recently worked on the go client update, could you take a look at this?

[christinaausley]

This is so CLEAN! Approving from a technical perspective.

[akeller]

I added @abbasadel's changes. Can I get a 👍 review so we can merge this?