Move geo_node_status data from individual columns to JSONB hash

What does this MR do?

We are going to use JSONB hash instead of individual columns. We also take care of smooth update here so if new fields in the hash is not set yet, it will use the old columns. In the next release, we will need to remove those columns from the database table (as well as backward compatibility tests).

Screenshots

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.

Closes #211630 (closed)