uncomment columns related to GoQuorum privacy

[macfarla]

Addresses database backwards compatibility broken by 067a263

Fixes org.rocksdb.RocksDBException: Column families not opened: error

See #5303

[github-actions]

• I thought about documentation and added the doc-change-required label to this PR if updates are required.
• I have considered running ./gradlew acceptanceTestNonMainnet locally if my PR affects non-mainnet modules.
• I thought about the changelog and included a changelog update if required.

[macfarla]

Testing

• create main/data by starting besu built with main 080fe87
• create 42f52e7/data by starting besu built with last good commit 42f52e7
• start besu-main with --data-path="42f52e72be25e75704d5116646369ae09860bb4a/data" - get column families not opened error (reproducing reported issue)
• create bring-back-column-fam/data by starting besu built with 402a004
• start besu-42f52e72be25e75704d5116646369ae09860bb4a with --data-path="bring-back-column-fam/data" - successful startup (new code works with new db)
• start besu-bring-back-column-fam with --data-path="42f52e72be25e75704d5116646369ae09860bb4a/data" - successful startup
• start besu-bring-back-column-fam with --data-path="080fe87c816ca3b4e1ba55eb7306d3ef323b75af/data" - successful startup

[jframe]

I tested locally as well and the old database is working again now.

[gfukushima]

Is it worth trying in a later PR something to drop/destroy these column families? Instead of just keep them for backwards compatibility?

[macfarla]

Is it worth trying in a later PR something to drop/destroy these column families? Instead of just keep them for backwards compatibility?

Maybe! I am not a database expert (clearly) so not sure of the pros and cons of this