Stop fetching emsdk from conda-forge

[anutosh491]

Description

emsdk's recipe from conda-forge is no longer being maintained. Hence preferably we should clone it and install it accordingly.

Type of change

Please tick all options which are relevant.

• Bug fix
• New feature
• Added/removed dependencies
• Required documentation updates

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 80.78%. Comparing base (e9df705) to head (426ce27).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #170   +/-   ##
=======================================
  Coverage   80.78%   80.78%           
=======================================
  Files          19       19           
  Lines         973      973           
  Branches       93       93           
=======================================
  Hits          786      786           
  Misses        187      187           

[mcbarton]

@anutosh491 why are we still using 3.1.45 when the latest version is 3.1.71?

[anutosh491]

Hi @mcbarton

I discussed the need for this PR on discord (pasting the link here)
Let me know if can't access it, in that case I shall paste the contents here.

Also answering your question. The whole jupyter stack (xeus, xeus kernels and compiler/interpreter frameworks in the backend) all are compiled against either 3.1.45 or 3.1.58 when being hosted on emscripten-forge. It is also generally recommended to have the whole toolchain built against the same version. So now that xeus and cppinterop are built against 3.145 as can be seen here it would be best to build the middleware, xeus-cpp against it too.

This is a temporary thing and would be updated to the later version soon (basically when everything moves to the latest version)