[HBase] construct an index table for SSO names

[JulienPeloton]

Describe the issue

Based on all ssnamenr extracted during the creation of the SSOFT, create a table in HBase whose indices will be the concatenation of:

• resolved numbers by quaero
• resolved names by quaero
• raw ssnamenr for unresolved objects

I'm explicitly not including aliases here. This corresponds to 1,057,031 entries as of 2023/12. The payload will contain a unique column containing the corresponding ssnamenr. This table will then serve for the name resolver.

[JulienPeloton]

For information (2023/12):

Number of (unique) SSO objects in Fink: 565,045

STATISTIC FROM QUAERO
-------------------------------------
Number of numbered objects: 491,986
  --> Number of objects with no number: 73,059
    --> Number of objects with only prov. designation: 72,915
    --> Number of objects unindentified by quaero: 144

As of now, we have 565,045 unique SSO objects (that is with a ssnamenr). Out of this, 491,986 have their ssnamenr as a proper number (int type). The vast majority of the remaining objects have only a provisional designation (72,915), and there is a small part unidentified by quaero (144). By inspecting, I found that these are either comets (107 objects, not resolved explicitly by quaero), or genuinely not found objects in quaero.

[JulienPeloton]

Fixed in

• SSO index table #774
• [HBase] update resolver tables #776

[JulienPeloton]

for information (2024/10)

Number of (unique) SSO objects in Fink: 596,216

    STATISTIC FROM QUAERO
    -------------------------------------
    Number of numbered objects: 547,922
    --> Number of objects with no number: 48,294
        --> Number of objects with only prov. designation: 48,155
        --> Number of objects unindentified by quaero: 139