[Feature]: Default region for Terminal API URL

Feature summary

Add a default region for Terminal API in LIVE

Problem statement

Currently, region need to specified for LIVE env if not, there will be no default region URL defined and this will lead to "URL Invalid" error

if (!this.config.environment) {
            throw new Error("Environment must be defined");
        }

        // set Terminal API endpoints 
        if (this.config.environment === EnvironmentEnum.TEST) {
            // one TEST endpoint for all regions
            this.config.terminalApiCloudEndpoint = TERMINAL_API_ENDPOINT_TEST;
        } else if (this.config.environment === EnvironmentEnum.LIVE) {
            // region-based LIVE endpoints
            if(this.config.region) {
                if (!Config.isRegionValid(this.config.region)) {
                    throw new Error(`Invalid region provided: ${this.config.region}`);
                }
                this.config.terminalApiCloudEndpoint = Config.getTerminalApiEndpoint(this.config.region);  
            }
        }

Proposed solution

Implement the same solution as seen in Java Library

// For LIVE environment, lookup the endpoint using the map
    if (environment.equals(Environment.LIVE)) {
      if (region == null) {
        return Region.TERMINAL_API_ENDPOINTS_MAPPING.get(Region.EU);
      }
      if (!Region.TERMINAL_API_ENDPOINTS_MAPPING.containsKey(region)) {
        throw new IllegalArgumentException(
            "TerminalAPI endpoint for " + region + " is not supported yet");
      }
      return Region.TERMINAL_API_ENDPOINTS_MAPPING.getOrDefault(region, TERMINAL_API_ENDPOINT_LIVE);
    }

Alternatives considered

No response

Additional context

No response

Start at the TypeScript Config logic around EnvironmentEnum.LIVE and terminalApiCloudEndpoint, comparing the proposed behavior with the Java Library example. Done when LIVE without a region uses the EU endpoint while unsupported explicit regions still produce the appropriate validation error.