Add version parameter to the get_metadata function for SingleTableSynthesizers

[pvk-developer]

Resolves #2484
CU-86b4tehv8

[sdv-team]

Task linked: CU-86b4tehv8 SDV - Add 'version' parameter to SingleTableSynthesizer.get_metadata #2484

[gsheni]

@pvk-developer should the target branch be feature/single-table-CAG?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.60%. Comparing base (28b2495) to head (9a710a4).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2491   +/-   ##
=======================================
  Coverage   98.60%   98.60%           
=======================================
  Files          59       59           
  Lines        6234     6238    +4     
=======================================
+ Hits         6147     6151    +4     
  Misses         87       87           

Flag	Coverage Δ
integration	82.49% <80.00%> (-0.03%)	⬇️
unit	97.51% <100.00%> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[pvk-developer]

@pvk-developer should the target branch be feature/single-table-CAG?

I did not point to that branch because we have self._original_metadata and self.metadata in main already, @amontanez24 should I move it ?

[amontanez24]

@pvk-developer should the target branch be feature/single-table-CAG?

I did not point to that branch because we have self._original_metadata and self.metadata in main already, @amontanez24 should I move it ?

Yes, we should point to that feature branch. Can you rebase that feature branch onto main and handle any merge conflicts there?