fix: handle Infura APIs based on application environment

[meKushdeepSingh]

This PR addresses the handling of Infura APIs according to the application environment (staging and production). It ensures that the appropriate Infura API & project IDs are used based on the environment configuration.

[github-actions]

• The variable name SHOW_CONSOLE is misleading, it's not about showing or disabling console, it should be renamed to something more descriptive.

• There is a typo in the comment All Server related endpoints, it should be All server-related endpoints.

• In the third-party services section, CNS_ENDPOINT seems to be undefined. Make sure it is imported correctly, or define it if it's supposed to be a constant.

• The assignment of ENDPOINT_ICE_SERVERS is missing a value to assign.

• The logic for CHAIN_ID seems potentially incorrect. Make sure it's supposed to have the value 1 for prod and 11155111 for staging.

• It's a good practice to use descriptive key names for objects. Consider renaming DAPP_URL to something more informative.

• The variable GC_RPC appears to be used, but it's not defined in the code provided. Ensure it is defined or removed if unnecessary.

• In the last line, the spread operator {...PROD_CONTRACTS} and {...STAGING_CONTRACTS} are used inside curly braces. This syntax is not correct for spreading objects. It should be spread without curly braces.

After addressing these issues, the code should be reviewed again for further improvements as necessary. If everything is corrected, please write 'All looks good.'

[gitpoap-bot]

Congrats, your important contribution to this open-source project has earned you a GitPOAP!

GitPOAP: 2024 Push Protocol Contributor:

Head to gitpoap.io & connect your GitHub account to mint!

Learn more about GitPOAPs here.