CCOL-2440: Add consumer configuration to save associated keys prior to saving primary record

[lionelpereira]

Pull Request Template

Description

Normal bulk consumption logic:

Widget:
has_one : detail

1. Record class records (Widget) are saved
2. Record class primary keys are filled from DB
3. Associated records (Details) are updated with foreign key from record class

Backfill consumption logic (this change)

FidgetWidget
belongs_to: widget
belong_to: fidget

Notes:

• Record class cannot be upserted first as foreign_keys widget_id, fidget_id are required

1. Associated records (Widget & Fidget) are created and linked to record class (FidgetWidget)
2. Associated records are saved
3. Primary keys (widget_id, fidget_id) of associated records are filled from DB
4. Foreign keys of record class are filled with newly saved primary keys of associated records

• [ ] Bug fix (non-breaking change which fixes an issue)
• [X] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• [ ] Test A
• [ ] Test B

Checklist:

• [ ] My code follows the style guidelines of this project
• [ ] I have performed a self-review of my own code
• [ ] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [X] I have added a line in the CHANGELOG describing this change, under the UNRELEASED heading
• [ ] My changes generate no new warnings
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] New and existing unit tests pass locally with my changes
• [ ] Any dependent changes have been merged and published in downstream modules

[dorner]

@lionelpereira can you provide some more information in this PR as to what the use case is here and why it isn't covered by existing functionality?

[lionelpereira]

@lionelpereira can you provide some more information in this PR as to what the use case is here and why it isn't covered by existing functionality?

@dorner Updated the PR description