Regenerate stale tie scores and populate the Boundary Checks section

[gronke]

Regenerates the score files against the reference calculator at RedHatProductSecurity/cvss-v4-calculator@d1eafe06 (the merge commit of the 2024-11-01 rounding fix, PR #67), and populates the empty Boundary Checks section.

• 159 reference-scores and 1,412 base-threat-scores entries move up one tenth (x.x5 tie rounding); no severity changes. macro-scores is already correct and is untouched.
• The 33 comment/blank lines in reference-scores that read Invalid vector string now mirror their vector-file counterparts, so the two files stay line-aligned without artifacts.
• All 25,028 negative-test error entries are byte-for-byte untouched.
• vectorFiles/regenerate_scores.mjs reproduces the score files against the sha256-pinned calculator revision; fetching cvss40.js at that revision is its only network access. On top of the calculator it enforces the eleven mandatory base metrics itself (the pinned revision accepts truncated vectors; reported upstream) and preserves existing error entries verbatim when it agrees a line is invalid.
• Second commit (separable): reference-vectors gains the 522 Boundary Checks base vectors whose pre-rounded score sits at an x.x5 tie, with expected scores in the aligned lines of reference-scores. Verified against the pre-fix calculator at bea2884: every one of the 522 scores exactly 0.1 lower there, so any implementation without the rounding fix fails the whole section.