feat: Add programmatic descriptions parser for [AtlasProxy]

[mgorsk1]

Summary of Changes

This MR introduces parsing of programmatic descriptions using parameters field of Table entity in Atlas Proxy. The parameters field is a map of String -> Any and seems like a perfect fit for this usecase.

Moreover, this property can be set for example on hive_table entity programatically with spark sql:

ALTER [TABLE|VIEW] table_name SET TBLPROPERTIES (key1=val1, key2=val2, ...) - Atlas hive-hook will propagate such action in Hive Metastore to Atlas metadata

All of those key1, key2 etc then become programmatic description entries.

The idea is also to have a filter to remove unwanted properties (like spark technical ones that appear in parameters after creating table with spark). This could also be of use for other proxies.

Tests

Tested for presence and filtering of programmatic desriptions.

Documentation

What documentation did you add or modify and why? Add any relevant links then remove this line

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
• PR passes make test

[mgorsk1]

cc @verdan

[codecov-commenter]

Codecov Report

Merging #152 into master will increase coverage by 0.34%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #152      +/-   ##
==========================================
+ Coverage   72.91%   73.25%   +0.34%     
==========================================
  Files          26       26              
  Lines        1233     1249      +16     
  Branches      128      132       +4     
==========================================
+ Hits          899      915      +16     
  Misses        307      307              
  Partials       27       27              

Impacted Files	Coverage Δ
metadata_service/config.py	100.00% <100.00%> (ø)
metadata_service/proxy/atlas_proxy.py	84.49% <100.00%> (+0.95%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5a8c117...73c81c9. Read the comment docs.

[feng-tao]

cc @verdan

[verdan]

a few comments

[verdan]

👍 LGTM

[pPanda-beta]

@mgorsk1
I see there is a particular part which breaks the camel case field into space separated words. Looks like an UI logic. Any particular reason to make it mandatory in the metadata service instead of frontend?

Source:

amundsenmetadatalibrary/metadata_service/proxy/atlas_proxy.py

Line 961 in 8c1b998

source = re.sub("([a-z])([A-Z])", "\g<1> \g<2>", source).lower()

My previous comment on test case:

e8b46a4#r42358611