Docs: the README says the benchmark tooling stays in the old repository, and the CI page lacks the engine tag for JVM wheels #402

I swept the documentation against what is settled now. Two statements need a change.

• README.md (Where this code comes from) says the benchmark tooling of humemai/arcadedb-embedded-python stays there. The benchmark harness moved to humemai/mmdbbench, and the old repository is retiring.
• docs/modules/ROOT/pages/development/ci.adoc says that test-jvm.yml takes the engine jars from the image tag latest by default, but not what that means for a wheel that is compared with a release. A JVM wheel built without -f arcadedb-tag=26.11.1 carries another engine than 26.11.1.post3, so an A/B or a gate run on it measures the engine as well as the change. The page should give the dispatch command.

I fix both in one pull request. The release pages already say that 26.11.1.post3 is published, so nothing else needed a change.