refactor: Make bloc implementations private

[provokateurin]

Some places accessed parts of Blocs that should have been in the interface. Now it is no longer possible to do that.

[Leptopoda]

I think that the interfaces should be sealed.

1. I don't like interface classes with constructors/factories
2. We prevent our users to extend these interfaces.

Long term the concrete implementations should not contain private fields as the classes themselves are already private. You already did so for the TimerBloc. But please not in this PR as it's already large enoguh :)

[provokateurin]

I don't like interface classes with constructors/factories

How should I fix it?

Long term the concrete implementations should not contain private fields as the classes themselves are already private

Agreed, I didn't do it to keep the diff more readable.

[Leptopoda]

How should I fix it?

a sealed class can no longer have the interface modifier :)
So just make them sealed as suggested in the review.

[provokateurin]

But that doesn't make the factories go away, no? I thought you saw that as a problem too.

[Leptopoda]

I'm fine with them :)

[provokateurin]

Making the classes sealed prevents us from creating mocks (at least with mocktail) :/

I think we should still go for it as we shouldn't need to have mocks for blocs once we untangle them.

[Leptopoda]

Making the classes sealed prevents us from creating mocks (at least with mocktail) :/

I haven't tried it yet and don't know if it would help but meta also has a sealed annotation. This would only produce lint warnings instead of compile time errors when one tries to extend it. Maybe this is a better idea 🤔

[Leptopoda]

I'll review this later today