Stop publishing core-tests and streams-tests

[ghostdogpr]

We want to stop publishing our tests, but we can't because they are currently used by the interop libraries.

Step 1:

Stop depending on core-tests in interop libraries. If it was actually used, replace it with ZIO Test.

• Interop Twitter
• Interop Scalaz
• Interop Monix
• Interop Java
• Interop Guava

(cats and reactive-streams are already not using it)

Example of using ZIO Test here: https://zio.dev/docs/usecases/usecases_testing

Step 2:

Stop publishing core-tests and streams-tests

[vilu]

I would like to tackle this one.

[ghostdogpr]

@vilu Thanks! Let us know if you need any help.

[ghostdogpr]

@vilu which interop are you tackling first? I ask in case other contributors want to share the work.

[vilu]

I work from the top to the bottom. I'll post a PR to the Twitter one this weekend to get a confirmation that I'm addressing it in the right way.

I can keep updating this PR when I pick a new one. So, just to re-iterate I'm currently working on the Twitter one. Any other one would be ok for anyone to pick up without us stepping on each others toes.

[ghostdogpr]

@vilu sounds good 👌

[mijicd]

@vilu just link this issue in your PRs and feel free to reach out if you need any help.

[vilu]

I actually ran into some issues: zio/interop-twitter#29 would love some feedback here.

[ghostdogpr]

Working on interop-java

[ghostdogpr]

Monix and Java done

[sideeffffect]

will do guava

[sideeffffect]

guava done zio/interop-guava#3

[ghostdogpr]

Step 1 completed