docs(descriptor): the Linux requirements describe the registry build, then the release binary

[singhpratech]

The registry page describes the binary the registry builds and serves. The hardware_requirements Linux passage described this project's own release binary instead: x86-64 only and a glibc 2.34 floor.

Facts: the registry builds linux_amd64 and linux_arm64 in its own image, and the amd64 binary it produced was measured with a GLIBC_2.14 symbol floor. x86-64, glibc 2.34, static libstdc++ and the CUDA build are properties of the release binary and the pip wheel. The libgomp.so.1 requirement is true of the registry build.

The passage now leads with what holds for the registry build (libgomp.so.1 at load time, with the apt/dnf hints and the exact LOAD error), states no glibc floor for it, and ends with one sentence for the release binary and the wheel (x86-64, glibc 2.34 or newer; the wheel bundles its own libgomp).

Only that passage changed, plus a dated entry in docs/RESEARCH_NOTES.md. extension:, repo:, version, toolchains and excluded_platforms are untouched. docs/INSTALL.md already attributes the glibc floor to the release binary and the wheel, and already says the libgomp requirement applies to both builds, so it needed no change.