This changes the error when using non-existant arguments in blackboxes 
from:

  Blackbox required at least 32 arguments, but only 8 were passed.

to the new error:

  Blackbox used "~ISSYNC[31]" , but only 8 arguments were passed.

So it'll be easier to keep the temp directory

It now correctly "escapes" square brackets in the right places.
And correctly brackets the second argument of ~SIGD

  Utility that can convert blackboxes from clash-lib .primitives.yaml files
  to InlineYamlPrimitive ANNotations.

You can now use ~PERIOD, ~ISSYNC, ~ISINITDEFINED and ~ACTIVEEDGE
on arguments of type Clock,Reset,Enable,ClockN and DiffClock.

This allows the removal of the KnownDomain constraint on
functions which take a Clock and/or a Reset/
Which is most of them.

The only functions that still need a KnownDomain constraint
should be the ones creating Clocks and/or Resets.

 * ZKnownDomain is used only blackboxes, it used to replace the KnownDomain there,
   so we can postpone the renumbering of arguments

For the more complex ones I've replaced KnownDomain
with the a dummy ZKnownDomain constraint,
so the argument numbers stay the same for now.

For some functions we add explicit foralls, so the order of the type 
arguments stays the same.

You don't need to provide a KnownDomain anymore

The conversion was done automatically by running:
  cabal run -- prim-yaml-to-inlineyaml
Clash.Explicit.BlockRam.blockRamU# Clash.Explicit.BlockRam.blockRam1#
Clash.Explicit.BlockRam.blockRam#
Clash.Explicit.BlockRam.Blob.blockRamBlob#
Clash.Explicit.BlockRam.File.blockRamFile# Clash.Explicit.RAM.asyncRam#
Clash.Explicit.ROM.rom# Clash.Explicit.ROM.Blob.romBlob#
Clash.Explicit.ROM.File.romFile# Clash.Explicit.Testbench.assert
Clash.Explicit.Testbench.assertBitVector Clash.Signal.Internal.delay#
Clash.Signal.Internal.register# Clash.Signal.Internal.asyncRegister#

Then the annotations were manually moved to be next to their haskell
definitions.

Current doctest(-parallel) can't pickup such defines automatically, so 
we have to do it manually.

And also define CLASH_OPAQUE, to prevent a ton of warnings.