Use https for outlink

[dakotabenjamin]

Partially fixes #5925

This PR updates the protocol to https. I have also updated the ORG_URL in CircleCI Context for staging and production to be "www.hotosm.org"

The reason we can't easily setup a redirect is from AWS:

Unlike a CNAME record, you can create an alias record at the top node of a DNS namespace, also known as the zone apex. For example, if you register the DNS name example.com, the zone apex is example.com. You can't create a CNAME record for example.com, but you can create an alias record for example.com that routes traffic to www.example.com (as long as the record type for www.example.com is not of type CNAME).

If this is not sufficient, we may be able to setup a redirect, but I would prefer not to, as this will likely change soon with the new hotosm website.

[HelNershingThapa]

I have also updated the ORG_URL in CircleCI Context for staging and production to be "www.hotosm.org"

This change resolves the issue at hand without requiring an additional protocol change. This change alone is sufficient to fix the problem, right?

Do you think it'd be important to consider the impact on forks that rely on HTTP rather than HTTPS for their sites? They may face difficulties in updating their site links. Is it accurate to say that this change could potentially affect these forks?

Instead of explicitly specifying the protocol in the code, why not retrieve the complete URL from an environment variable? By doing so, the protocol can be dynamically set based on the environment, providing more flexibility. Thoughts?

[dakotabenjamin]

You are correct that this change is not required to fix the issue, we just need to push a deployment with the new context envvar.

However, it is my personal opinion that we should not be supporting HTTP in general. Your suggestion to make the whole url with the protocol a part of the envvar is well taken, and I will push a change to reflect that. We will need to parse out the domain to make it look pretty, though, or call it "HOTOSM Homepage" or something to that effect. What do you think?

[HelNershingThapa]

we just need to push a deployment with the new context envvar.

Could you also revise the ORG_PRIVACY_POLICY_URL when you do that, please? The privacy policy links would also need some amendments. I can make and push those changes to update the privacy policy URLs in the frontend to use HTTPS consistently in this PR.

We will need to parse out the domain to make it look pretty, though, or call it "HOTOSM Homepage" or something to that effect. What do you think?

I agree that we'd need to parse out that domain. I like hotosm.org being displayed just like it is now.

[dakotabenjamin]

New change looks like this:

[HelNershingThapa]

This test case should have failed, but it did not 🤨.

tasking-manager/frontend/src/components/header/tests/index.test.js

Lines 25 to 28 in fc5f390

	if (ORG_URL) {
	expect(screen.getByText(ORG_URL)).toBeInTheDocument();
	expect(screen.getByText(ORG_URL).closest('a')).toHaveAttribute('href', `http://${ORG_URL}`);
	}

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication