Update & Rework Dependencies

[thopkins32]

With #318 , we will soon have two optimizer backends in Blop. Therefore, it is time to create a more modular dependency tree with optional extras for ax and qs.

The base dependencies of Blop now only refer to the essentials required for accessing the Bluesky plans and callbacks that nearly every Blop user would use.

If someone wants to use the Ax backend, they can install the blop[ax] extra.
If someone wants to use queueserver, they can install the blop[qs] extra.
Soon, they can choose to install blop[xopt] extra.

Changing these dependencies to be extras creates some breaking changes to import paths. Functionality-wise, nothing changes in this PR.

We also drop support for Python 3.10, since botorch does in their latest release.

Closes #320
Closes #319

[checkmarx-gh-ast-us-povs]

Checkmarx One – Scan Summary & Details – 973684c4-480d-4240-8726-45c9ed700f8e

Great job! No new security vulnerabilities introduced in this pull request

---

Communicate with Checkmarx by submitting a PR comment with @Checkmarx followed by one of the supported commands. Learn about the supported commands here.

[MTakahashi-KWH]

Functionally the same. This also addresses the last dangling "_id" to ID_KEY concern.

would note it may be worth providing a blop[standalone], blop[aio], or blop[all] configuration, or perhaps a default packageless agent that randomly samples the configuration space. That would give users coming from Bluesky a single-import way to experiment with the library without immediately confronting them to choose and install a secondary package just to run Blop.

In general, i think any package configuration should support a standalone mode so its components can be explored and evaluated in isolation. (extremely helpful for new and less technical users, since most will first download blop or blop[all])

[josephhanrahan]

I agree with @MTakahashi-KWH. Given this arrangement, having something like [base] and [all] becomes important for installation. Otherwise looks good.

[thopkins32]

@josephhanrahan @MTakahashi-KWH Fair points. How about the following? This can go on the installation docs page.

Extra	Installs	Notes
blop[ax]	ax-platform, botorch, gpytorch, torch	GPU torch by default; pair with [cpu] for CPU-only
blop[xopt]	xopt	Coming soon
blop[scipy]	scipy	Coming soon
blop[queueserver]	bluesky-queueserver-api	Transport layer only; pair with [ax] for QueueserverAgent
blop[cpu]	(uv index routing)	Routes torch to the CPU-only PyTorch index; requires uv
blop[all]	All backends + [queueserver]	No dev tooling; will grow as new backends are added
blop[dev]	blop[all] + dev tooling	For contributors