fix(dynamite): test documentation of generated libraries

[Leptopoda]

Currently depends on the next release of code_builder.
Once it is done I'll regenerate the specs for every commit and drop the current dependency overrides.

pana output for nextcloud: 7701 out of 20941 API elements (36.8 %) have documentation comments.

[provokateurin]

Would it be possible to already separate and merge some of the commits?

[Leptopoda]

I think all other than 885b6c1 (and the documentation unit test) would already be possible.
Do you prefer single PRs per commit or one with al changes?

[provokateurin]

Just group them in a way you think makes sense :)

[Leptopoda]

looks like we'll get a release really soon
dart-archive/code_builder#445

[Leptopoda]

just a rebase for now.
@provokateurin our current dynamite code does not allow easily documenting interfaces or typedefs. Should I just add a local ignore for them?

[provokateurin]

our current dynamite code does not allow easily documenting interfaces or typedefs. Should I just add a local ignore for them?

Can you explain to me why? I'm fine with an ignore if there is nothing better right now.

[Leptopoda]

1. only direct interfaces have doc comments. All interfaces generated by AllOfs can't be documented.
2. adding them to top level typedefs would require adding a docs field to the TypeResult that is only used by the typedefs.
   I don't like having it in there as it would only further clutter the typeresults

[provokateurin]

Now we need to add a latin dictionary 😂

[provokateurin]

The links to the licenses should be quoted to avoid the final dot being part of the link.