Add zstd for wasm build

[trungleduc]

Needed for emscripten-forge/pyjs#76

[trungleduc]

@martinRenou @JohanMabille do you know if the failed tests are related to my changes?

[anutosh491]

It seems the error comes out of this test

xeus-python/test/test_debugger.cpp

Line 1246 in 8725149

TEST_CASE("external_next_continue")

If you need this to go in, maybe you could comment this and add a TODO ?

[anutosh491]

It seems some specific operations might be going wrong (first external_next_continue fails and now next_continue)
We had all tests working as expected during the last release. Haven't looked into it but not sure why some tests fail now.

@trungleduc could you check and add todo's for the failing ones. I shall look into them once that is done !

[anutosh491]

I guess we can do what you did but what I meant was to only comment out the tests that fail (I guess a couple would fail) and add todos for only what fails

Otherwise a better way to do this might be to comment this out and add a todo

xeus-python/.github/workflows/main.yml

Lines 71 to 74 in 8725149

	- name: Test xeus-python C++
	run: ./test_xeus_python
	timeout-minutes: 4
	working-directory: build/test

And these out

xeus-python/test/CMakeLists.txt

Lines 53 to 55 in 8725149

	test_debugger.cpp
	xeus_client.hpp
	xeus_client.cpp

So that we don't end up with this and we know the tests need to be fixed.

Run ./test_xeus_python
[doctest] doctest version is "2.4.11"
[doctest] run with "--help" for options
===============================================================================
[doctest] test cases: 0 | 0 passed | 0 failed | 0 skipped
[doctest] assertions: 0 | 0 passed | 0 failed |
[doctest] Status: SUCCESS!

[trungleduc]

@anutosh491 is it ok now?

[JohanMabille]

The failures of the debugger tests are not related to your changes. I think we can merge this one and investigate the failing tests in a dedicated PR.