fix(ci): add lycheeignore entries and disable noisy Vale rules

Link checker:
- Exclude pre-existing broken EVES-003 URLs (fixed in EVM feature PR):
  docs.pinata.cloud/web3, GAIA-X4PLC-AAD/ontology-management-base
- Exclude conventionalcommits.org (intermittent connection resets in CI)

Vale:
- Disable write-good.Passive, Google.Passive (passive voice is standard
  in normative specs: "MUST be derived from...")
- Disable write-good.E-Prime (avoid is/are/was — incompatible with specs)
- Disable write-good.TooWordy ("however", "indicate" are normal terms)
- Disable Google.Headings (specs use title-case: "Backwards Compatibility")
- Disable Google.Contractions (specs MUST NOT use contractions)
- Disable Google.Parens, Google.Semicolons (common in spec prose)

Signed-off-by: jdsika <carlo.van-driesten@vdl.digital>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: jdsika

.lycheeignore

@@ -8,3 +8,10 @@ https://ipfs.envited-x.net/
 
 # GitLab blocks automated requests with 403
 https://gitlab.com/tezos/tzip/
+
+# Pre-existing broken links in EVES-003 (fixed in EVM feature PR)
+https://docs.pinata.cloud/web3/
+https://github.com/GAIA-X4PLC-AAD/ontology-management-base/
+
+# Flaky external sites (intermittent connection resets in CI)
+https://www.conventionalcommits.org/

.vale.ini

@@ -22,3 +22,18 @@ proselint.Typography = NO
 Google.Spacing = NO
 # Occasional emphasis is acceptable in specs
 Google.Exclamation = NO
+# Passive voice is standard in normative specifications ("MUST be derived from...")
+write-good.Passive = NO
+Google.Passive = NO
+# E-Prime ("avoid is/are/was") is incompatible with specification language
+write-good.E-Prime = NO
+# "however", "indicate", "requirement" are normal technical terms
+write-good.TooWordy = NO
+# Specs use title-case section headings (e.g. "Backwards Compatibility")
+Google.Headings = NO
+# Specs MUST NOT use contractions per formal writing conventions
+Google.Contractions = NO
+# Parenthetical clarifications are common in specs
+Google.Parens = NO
+# Semicolons are appropriate in complex specification sentences
+Google.Semicolons = NO