Clean out the static frontend

[jonkafton]

What are the relevant tickets?

https://github.com/mitodl/hq/issues/5846

Description (What does it do?)

Removes the ./frontends/mit-learn workspace and any references. This was the entrypoint for the previous static frontend, now replaced by the Next.js entrypoint at ./frontends/main.

Also removes the E2E/browser tests as these have been inactive and have not been migrated to work with Next.js.

How can this be tested?

Generally, all tests should pass on frontend and backend and services should build and run with Docker without error.

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
9430286	Triggered	Generic Password	2b15331	docker-compose-e2e-tests.yml	View secret
9430286	Triggered	Generic Password	2b15331	docker-compose-e2e-tests.yml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[jonkafton]

Is this needed for anything?

[ChristopherChudzicki]

It was necessary when django served the JS

[jonkafton]

Is this needed for anything?

[ChristopherChudzicki]

Only back when django served the JS

[jonkafton]

I've added a blank.png at this path, but do we actually need it for this test? It's not used in the frontend.

[ChristopherChudzicki]

It's "supposed" to be the fallback for embedly. See frontends/ol-utilities/src/learning-resources/learning-resources.ts

That said:

• we don't need the /static version
• The version we do have set isn't working right now (https://rc.learn.mit.edu/static/images/blank.png) ... unsure why
  • EDIT: I forgot I was on your branch. The link I posted does not work, but should after this release, I think.

[ChristopherChudzicki]

Approved, but could you change the url in

const BLANK_IMAGE = "https://rc.learn.mit.edu/static/images/blank.png"

to use NEXT_PUBLIC_ORIGIN