Review of Structs Naming Convention + Callback Processing Example

[dvonthenen]

Proposed changes

Changes:

• Implements example code of the callback processing found here: https://developers.deepgram.com/docs/callback/
• Adds omitempty to all nodes in struct in the event that there are times in which certain fields aren't required. This solves any issues with JSON parsing and gives best-effort return on values
• Internal variable name changes from Result_id to ResultID to fix issues with Go naming conventions. Do this for all the names. This will trigger errors when we add the linter for Go.
• It seems like there are a couple of different definitions of what Summary object is. This is an attempt to keep both definitions to maintain backwards compatibility within the SDK.

Types of changes

What types of changes does your code introduce to the community Go SDK?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update or tests (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING doc
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• Any dependent changes have been merged and published in downstream modules

Further comments

NA