Use BepinEx Nuget package feed for assembly references

[xiaoxiao921]

Remove most of the dlls from libs/ folder since its now handled through the bepinex nuget feed

[harbingerofme]

@tristanmcpherson can we run a pipeline on this to test if it works?

[tristanmcpherson]

Can we still support this?

[xiaoxiao921]

We totally can. The issue currently is that the unity core dlls in this repo are not stripped which allow the construct of the objects. But the dlls in the bepinex nuget feeds are all stripped.
We either get rid of the r2api dotnet tests and move them to a project that we would test through a game launch instead of having them launched in a GitHub action.
Or we change the GitHub action so that it replaces the stubbed dlls with non stubbed ones from the dedicated server installation ( which is free ) and run the tests with those.

I personally prefer the first solution much more as we would be able to test all submodules properly and it's something done in a lot of other modding communities too. From Terraria to Valheim ( basically an ultimate ExampleMod that covers basically all different apis available )

[xiaoxiao921]

New commits :

• R2API.Test are not called from the github action anymore, instead, a bepinex dll test plugin is made available in the Artifact output and contains xunit tests that are called when launching the game.
• It'll allow for much powerful tests as we are in the same environement the api is used in normally and the submodules hooks will be tested with the game code which is arguably the biggest point of potential failure

[tristanmcpherson]

There should be a dash before uses here