Docs(Go): Adding Go folder and solutions

[es-codigo]

Docs(Go): Adding Go folder and solutions

[Destiny-02]

Hi @es-codigo, thank you for making a PR to the solutions repository! Please check the below change(s) requested:

Stay true to existing variable/function naming, code comments and algorithm structure. Feel free to add additional comments for clarity, especially if any language-specific nuances are included.

Please add code comments to the Go solutions. The comments should match the comments from the official Python solutions.

Thanks again for your contributions! 🙂

[ineBallardin]

@es-codigo @Destiny-02

There is no strict rule in the official Go documentation regarding file naming conventions, but the commonly accepted practice in the Go community is to use snake_case for file names. You can find several examples following this pattern in the Go documentation here.

I noticed that you've used camel case for file names. Since I'm contributing to the chapter two solutions and aligning with @Destiny-02 in the Discord community, I believe it would be beneficial to standardize our naming conventions to maintain consistency throughout the project.

Would you be open to renaming the files to follow the Go idiomatic style using snake case? This will make the codebase more aligned with best practices and easier to navigate for future contributors.

[Destiny-02]

Closing this PR because most of the Two Pointers Go solutions have been merged. Feel free to open another PR for the remaining brute-force solutions in the Two Pointers chapter.