Specs: Improve blocks of texts with multiple expectations

  - id: :include_activitypub_context
    text: |
      ActivityPub defines some terms in addition to those provided by ActivityStreams.
      These terms are provided in the ActivityPub JSON-LD context at https://www.w3.org/ns/activitystreams.
      Implementers [[SHOULD]] include the ActivityPub context in their object definitions.
      Implementers MAY include additional context as appropriate.
  # Duplicate text, different ID
  - id: :include_additional_context
    text: |
      ActivityPub defines some terms in addition to those provided by ActivityStreams.
      These terms are provided in the ActivityPub JSON-LD context at https://www.w3.org/ns/activitystreams.
      Implementers SHOULD include the ActivityPub context in their object definitions.
      Implementers [[MAY]] include additional context as appropriate.
  - id: :activitypub_share_activitystream_uri
    text: ActivityPub shares the same URI / IRI conventions as in ActivityStreams.

we could have something like

  specs:
  - |
    ActivityPub defines some terms in addition to those provided by ActivityStreams.
    These terms are provided in the ActivityPub JSON-LD context at https://www.w3.org/ns/activitystreams.
    Implementers [[SHOULD]include_activitypub_context] include the ActivityPub context in their object definitions.
    Implementers [[MAY]include_additional_context] include additional context as appropriate.
  - id: :activitypub_share_activitystream_uri
    text: ActivityPub shares the same URI / IRI conventions as in ActivityStreams.

The report should render one line with the status of the different ids:

┌─────┬──────────────┬────────────┬───────────────┐
│ pass│  first_id    │ ...        │ Common text   │
├─────┼──────────────┼────────────┤               │
│ fail│  second_id   │ ...        │               │
├─────┼──────────────┼────────────┼───────────────┤
│ pass│  some_id     │ ...        │ Other text    │
└─────┴──────────────┴────────────┴───────────────┘