docs: docs site setup

[ccm32004]

configured documentation site for apache pulsar: https://numaproj-contrib.github.io/apache-pulsar-java/docs-site/

• rewrote some of the documentation to be less verbose
• added comments to classes for javadoc
• includes user facing docs for usage of apache pulsar, and developer facing docs (api reference, for class/method definitions)
• uses javadocs, which automatically takes comments and generates documents site
• user-facing docs (getting started, source/sink usage, testing) written as Markdown under docs/, rendered via MkDocs with the Material theme.
• added automated script that copies the site files into deployed branch gh-pages (builds Javadoc + MkDocs, publishes via a temporary gh-pages worktree).

Testing notes

• tested automated script to add new changes to site with no bugs

[github-actions]

Code Coverage

Percentage of source code lines executed by unit tests.

Overall Project	82.73%	✅
Files changed	100%	✅

File	Coverage
PulsarAdminProperties.java	100%	✅
PulsarAdminConfig.java	100%	✅
PulsarClientProperties.java	100%	✅
PulsarClientConfig.java	100%	✅
PulsarProducerProperties.java	100%	✅
EnvLookup.java	100%	✅
PulsarProducerConfig.java	93.51%	✅
PulsarConfigLoader.java	93.26%	✅
PulsarSink.java	78.86%	✅
PulsarSource.java	78.8%	✅
PulsarConsumerProperties.java	77.02%	✅
PulsarConsumerManager.java	61.9%	✅

[github-actions]

Continuous benchmark

Config: batch size = 500

Compared to the latest result on gh-pages (last main run that updated charts). Regression when a metric degrades by more than 2× vs baseline.

Metric	This run	Baseline (main)	Change	Status
Consumer Throughput	33116.67 msgs/sec	33833.33 msgs/sec	-2.1%	OK
Processing Latency (per batch)	15.11 ms	14.79 ms	+2.2%	OK
Read Latency (per batch)	7.53 ms	7.34 ms	+2.6%	OK
Ack Latency (per batch)	0.56 ms	0.54 ms	+3.7%	OK
Consumer CPU	1327 millicores	1323 millicores	+0.3%	OK
Consumer Memory	342 MiB	339 MiB	+0.9%	OK

Result: No regression beyond the threshold vs main baseline.

Workflow run
· GitHub Pages charts