test.cve.org no longer shows spaces in version ranges

[ElectricNroff]

This issue may currently be affecting the usability of test.cve.org by multiple CNAs. For example, this CVE Record:

{"dataType": "CVE_RECORD","dataVersion": "5.0","cveMetadata": {"cveId": "CVE-2024-20739",
"assignerOrgId": "b3476cb9-2e3d-41a6-98d0-0f47421a65b6","state": "PUBLISHED"},
"containers": {"cna": {"providerMetadata": {"orgId": "b3476cb9-2e3d-41a6-98d0-0f47421a65b6"},
"affected": [{"vendor": "v","product": "p","versions": [
{
  "version": "1234",
  "status": "affected",
  "lessThanOrEqual": "5678",
  "versionType": "custom"}]}],
"descriptions": [{"lang": "en","value": "acd def ghi"}],"references": [
{"url": "https://a.us"}]}}}

renders today with:

affected from1234through5678

whereas last week it would have rendered with:

affected from 1234 through 5678

[ElectricNroff]

I think this may fix the issue only for elements of the versions array where row.versionsChanges.length > 0 is true. For example, in the e1932df commit, the first two differences change {{word}} to {{word}}  but the third difference does not insert the  

In https://test.cve.org/CVERecord?id=CVE-2024-20694 the first element of the versions array looks wrong affected from3.6through3.6 but every other case looks OK, because every other case has a true value for row.versionsChanges.length > 0

[athu-tran]

@ElectricNroff Thanks for catching this. I'm going to fix this.