Chore/replace enums with companion pattern approach

[lukasaric]

Solves #1077

Motivation and Resolution

To increase the type safety, this PR introduces the enum replacement with the companion pattern approach.
To have a better understanding, here's a good thread on why it would be good to avoid enums in TS

Don't use Enums in Typescript, they are very dangerous

RPC version (if applicable)

Usage related changes

n.a

Development related changes

Here's the example of before vs after usage:

BEFORE

export enum NetworkName {
  SN_MAIN = 'SN_MAIN',
  SN_GOERLI = 'SN_GOERLI',
  SN_SEPOLIA = 'SN_SEPOLIA',
}

AFTER

export const NetworkName = {
  SN_MAIN: 'SN_MAIN',
  SN_GOERLI: 'SN_GOERLI',
  SN_SEPOLIA: 'SN_SEPOLIA',
} as const;

// eslint-disable-next-line @typescript-eslint/no-redeclare -- intentionally naming the variable the same as the type
export type NetworkName = (typeof NetworkName)[keyof typeof NetworkName];

Checklist:

• Performed a self-review of the code
• Rebased to the last commit of the target branch (or merged it into my branch)
• Linked the issues which this PR resolves
• Documented the changes in code (API docs will be generated automatically)
• Updated the tests
• All tests are passing

[tabaktoni]

lgtm