GeezerVison

Drop min_fps/max_fps from the public API

They budget NVL's layout steps per frame, not the render frame rate, and only bind
when a single layout step is expensive (tens of thousands of nodes) — below that the
per-frame loop's hard cap of 20 steps makes them a no-op. They are also ignored in
NVL's WebGL render-from-texture fast path, which is the natural setup for graphs
large enough for them to matter. Not worth the misleading, permanently-caveated API
surface; remove until there is a real need (or a general nvl_options passthrough).

Removes the params from render/render_widget/_build_render_options, the fields from
RenderOptions/NvlOptions, the test, the changelog bullet, and the notebook section.

Fix changelog detection logic

Use GDS client > 2.0 as new default version (#476)

* Use latest gds client version per default

* Update pre-release script

ignore dependabot script + a prior failed release

Rework release process

Rebuild js artifacts

Merge pull request #434 from neo4j/fix-gds-version-support

Fix gds tests for latest alpha release

Merge pull request #399 from neo4j/GDS-193

Add support for widget + streamlit

Fix gds tests

notebooks dont support 2.0a1 yet.
(will be updated once 2.0 is out)

Merge pull request #374 from neo4j/GDS-96

Add on_dangling parameter (warn by default)

Merge pull request #350 from neo4j/gds-261-detect-theme-change-after-…

…init

Detect theme changes after first render