In Frontend, Refactor Hardcoded Values to Use Constants or Configuration

[OhmSpectator]

Description

Currently, several components set the selected region to a hardcoded value of 'World' or check against it. This approach can lead to potential issues with maintainability and flexibility as the application scales or undergoes changes.

Suggested Improvement

Refactor the code to replace hardcoded strings and values with constants or configuration objects. This will centralize the management of these values and make the codebase more maintainable.

Implementation Details

• Create a constants.js file or a similar configuration file in the src directory.
• Define constants for commonly used values, such as default region names, IDs, and any other relevant information.
• Import and use these constants within the HierarchySwitcher component and any other components where hardcoded values are used.

Benefits

• Maintainability: Centralizing hardcoded values makes it easier to manage and update them.
• Scalability: As new features or hierarchies are added, having a single source of truth for these values simplifies the process.
• Best Practices: Aligns with best practices in React development for managing application-wide static data.

Acceptance Criteria

• No hardcoded strings or values are present in the components.
• All default values are sourced from a constants/configuration file.
• The application behaves as expected with no regressions in functionality.

[VishalD51]

@OhmSpectator I'm willing to work on this. Could you assign this issue to me, please?

[OhmSpectator]

@VishalD51 ok!

[VishalD51]

@OhmSpectator Can you please check this PR: #89
and Let me know if you want more changes regarding this. Thanks!

[OhmSpectator]

@VishalD51 thanks! I'll check the PR in the next few days.

[OhmSpectator]

The default zoom level (9) from RegionMap should also be added to the constants.