Remove dependency on old network version

[Kleidukos]

This allows us to remove the flag.
Fixes #160

[hsenag]

is it necessary to do this in the same PR?

[Kleidukos]

@hsenag It would be really appreciated to move to the standard SPDX identifier for the license.

[hsenag]

sure, but does it need to be done in the same commit/PR? Particularly the Cabal version bump which could cause noise if later trying to track down some problem caused by the dependency changes.

[Kleidukos]

@hsenag Cabal version change does not cause hard-to-debug problems because it conditions what version of the cabal library (through cabal-install or stack) can parse the file. Cabal 3.0 format support is around since 2019.

But I can separate the commit, yes.

[andreasabel]

@Kleidukos @hsenag I do not think it is good to require cabal-version: 3.0 on the one hand (Cabal 3.0 was shipped with GHC 8.8) and base >= 4.6 (GHC 7.6) on the other hand.
Why not do the minimal bump on cabal-version and sync it with a base bump? E.g. cabal-version: 2.0 and base >= 4.10, setting GHC 8.2 as the last supported GHC version.
Ideally, cabal-version should be independent from the Cabal version, but it is not in practice.

[hsenag]

I'll look into shipping this soon if nobody else gets there first.

[hsenag]

Shipped in 4000.5.0 - thanks for the fixes