Cardano Updates

- Add DataKinds extension to SendFaucetAssets.hs (-Wdata-kinds-tc)
- Remove redundant foldl' imports (now in Prelude with GHC 9.12)
- Fix remaining hlint Functor law hints

Signed-off-by: Chris Gianelloni <[email protected]>

Signed-off-by: Chris Gianelloni <[email protected]>

Signed-off-by: Chris Gianelloni <[email protected]>

Add Dijkstra pattern matches to all era-indexed functions, add
fromDijkstraCert/fromDijkstraPParams/fromDijkstraTxOut and related
functions, export Dijkstra type alias from Read.Eras, add PParamsType
entry, fix partial head warnings in test specs.

- Add MathJax configuration script (required for pymdownx.arithmatex
  generic mode to render)
- Add pull_request trigger to CI workflow (was only on push to master)
- Guard deploy job to only run on push to master
- Fix wrong equipartitionNatural example

Material theme with MathJax, mermaid diagrams, and 15 documentation
pages covering concepts, algorithms, math, and data structures.

Add PlutusV4 case to genCostModel, add ShelleyBasedEraDijkstra case
to protocolParametersForHashing, and migrate genTxCertificate from
deprecated Certificate API to Cardano.Api.Compatible.Certificate.

Add DijkstraEra (protocol version 12) to all era-indexed type families,
pattern matches, and generators in the read library. Also fix -Werror
warnings: remove redundant constraints, replace deprecated fromTxSeq
with txSeqBlockBodyL lens, and use reqSignerHashesTxBodyG for Dijkstra
where AtMostEra "Conway" prevents using the lens variant.

Bumps [qs](https://github.com/ljharb/qs) from 6.14.0 to 6.14.2.
- [Changelog](https://github.com/ljharb/qs/blob/main/CHANGELOG.md)
- [Commits](https://github.com/ljharb/qs/compare/v6.14.0...v6.14.2)

---
updated-dependencies:
- dependency-name: qs
  dependency-version: 6.14.2
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>

postgresql/generic.nix sets disallowedReferences = [ stdenv'.cc ] which
scans all outputs for references to the C compiler after build phases
complete. For musl cross-compilation, .pc files or .la files may retain
references to the cross-compiler toolchain path, causing the check to
fail silently — all build phases complete successfully with no error in
the log, but the build is recorded as failed.

This explains why postgresql-musl builds consistently "succeed" (all
phases including fixup and stripping complete) but are recorded as
failures on every builder, even with 400+ GB free disk space.

based on conversations at the [Dagstuhl seminar on behavioural types](https://www.dagstuhl.de/26071)

Signed-off-by: Roland Kuhn <[email protected]>