BREAKING: fix linter issues

[SuperManifolds]

Description

Changes the Polyglot errors to follow Go code style conventions for error names.
This change may break any external code that checks for specific Polyglot errors by name in their error handling

Fixes Issue FRPC-11

Type of change

• Refactor (non-breaking change which does not add functionality) [title: 'refactor:']
• Breaking change (fix, feature, or refactor that would change existing functionality or interfaces) [title: 'BREAKING CHANGE:']

Final Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• Any dependent changes have been merged and published in downstream modules
• I have checked my code and corrected any misspellings
• I have signed-off my commits with git commit -s (see the developer's certificate of origin)

[ShivanshVij]

LGTM!

These breaking changes will need to be updated throughout scale right?