build(deps): remove dokka, no longer in use

[mikehardy]

Purpose / Description

It doesn't appear that we actually use dokka anymore, remove the dependency

Fixes

• Closes build(deps): bump org.jetbrains.dokka from 1.9.20 to 2.0.0 #17612

Approach

Remove all references to dokka in our build files

How Has This Been Tested?

We use jitpack.io to publish the API artifacts, and in our jitpack.yml we run ./gradlew :api:publishToMavenLocal

Anki-Android/jitpack.yml

Line 15 in ff607b3

- ./gradlew :api:publishToMavenLocal

So I ran that then checked the javadoc artifact (attached) - it does generate (which is job number one) and it appears fine.

To be clear though, I'm not that interested in the output, it's mainly generated at all because some publishers (maven at least, jitpack unknown) require you to have a javadoc jar.

But we also publish the actual sources of the API module since we are open source, and most (all?) IDEs will auto-pull those and cross-link everything up and let you just open things and look. Which is 100 times more useful than javadoc and the primary reason why I haven't actually looked at anyone's javadoc in ages.

api-2.0.0-javadoc.zip

Learning (optional, can help others)

I'd almost forgotten that javadoc existed, but then I don't work much with closed-source products.

Checklist

Please, go through these checks before submitting the PR.

• You have a descriptive commit message with a short title (first line, max 50 chars).
• You have commented your code, particularly in hard-to-understand areas
• You have performed a self-review of your own code
• UI changes: include screenshots of all affected screens (in particular showing any new or changed strings)
• UI Changes: You have tested your change using the Google Accessibility Scanner

[david-allison]

I approve 3808c7c, but it feels like this PR needs a rebase before it goes in

[mikehardy]

yeah the other dependency-updates traffic blew this up

I just squashed dependency-updates to main
then I force-pushed dependency-updates after a reset --hard from main (so they were in sync post-squash)
then I took this branch and dropped all the single-commit dependency-updates before rebasing it from the newly-pushed dependency-updates with the squash

then I pushed that, so should be sparkly clean