feat and perf: Add support for Multiple Programmatic Descriptions and Table level Badges

[VoLKyyyOG]

Summary of Changes

Hey team, thanks for reviewing this PR! This is a newer PR with the correct sign-off.

The motivation originates from #1828 which makes the original code quite convoluted and creates duplicated nodes/records. However, with #1877 being an epic speed-up to the original Neo4JCSV process (hopefully the PR is merged soon), the original naive method of duplicating TableMetadata for multiple programmatic descriptions does not work.

The changes here aim to mitigate this issue and allow multiple programmatic descriptions to be added and also benefit from the significantly reduced runtime using APOC.

Change Log:

• Added support Table level Badges
• Added support for multiple programmatic descriptions to reduce duplicate calls to TableMetadata
• Added a sample script under example/scripts/sample_base_postgres_metadata_extractor for examples
• Added some extra comments that I felt were useful when reading through the code (they were quite sparse)
• In future, it may be worth deprecating the is_view flag and use the new badges argument instead (as its generalised). We've removed the flag from our prod instance without issues.

Example Changes:
(all sensitive info has been removed)

• Table Badges

• Programmatic Descriptions

Tests

The code has been tested and deployed in our prod environment and I am more than happy to have a quick knowledge share on my changes / tests. This consists of over 40 thousand tables and 500,000 thousand columns.

However testing from the core repo side would be appreciated as our Amundsen is greatly modified and as such, our environment will not capture all test cases.

CheckList

Make sure you have checked all steps below to ensure a timely review.

• PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"
  • In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.
• PR includes a summary of changes.
• PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
• In case of new functionality, my PR adds documentation that describes how to use it.
  • All the public functions and the classes in the PR contain docstrings that explain what it does

[VoLKyyyOG]

@chonyy fixed it!

[VoLKyyyOG]

Hmm looks like some issue with None being allowed through. Will resolve sometime soon.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[feng-tao]

@kristenarmes @dkunitsk @allisonsuarez could you all take a look?