feat: Disabled enforce Countly by env variable

[przemvs]

Description

Added flag to disable enforcing Countly.

Checklist

• mentions the JIRA issue in the PR name (Ex. WPB-423)
• PR has been self reviewed by the author;
• Hard-to-understand areas of the code have been commented;
• If it is a core feature, unit tests have been added;

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[V-Gira]

I feel like this would achieve the same thing:

Suggested change

	if (!DISABLE_ENFORCE_COUNTLY && (isDev || isEdge || isInternal || isLocalhost || isStaging)) {
	if (isEdge || isInternal || isStaging) {

We only want to enforce it on internal envs, not really dev envs

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Project coverage is 46.37%. Comparing base (0f86852) to head (7227f65).
Report is 28 commits behind head on dev.

Additional details and impacted files

@@            Coverage Diff             @@
##              dev   #18175      +/-   ##
==========================================
- Coverage   46.38%   46.37%   -0.02%     
==========================================
  Files         796      796              
  Lines       25790    25790              
  Branches     5884     5884              
==========================================
- Hits        11962    11959       -3     
- Misses      12331    12334       +3     
  Partials     1497     1497              

[aweiss-dev]

This PR should be dropped.

It used the "wrong" logic, to disable enforcement via a env variable. We already changed the enforcement to use a env variable instead of in-app logic