DPL Analysis: Rework table input record extraction

[aalkin]

• update InputRecord so that a ConcreteDataMatcher can be used to extract entries
• use ConcreteDataMatcher instead of binding throughout the Analysis Framework to access AOD+ tables in the input

[github-actions]

REQUEST FOR PRODUCTION RELEASES:
To request your PR to be included in production software, please add the corresponding labels called "async-" to your PR. Add the labels directly (if you have the permissions) or add a comment of the form (note that labels are separated by a ",")

+async-label <label1>, <label2>, !<label3> ...

This will add <label1> and <label2> and removes <label3>.

The following labels are available
async-2023-pbpb-apass4
async-2023-pp-apass4
async-2024-pp-apass1
async-2022-pp-apass7
async-2024-pp-cpass0
async-2024-PbPb-apass1
async-2024-ppRef-apass1
async-2024-PbPb-apass2
async-2023-PbPb-apass5

[aalkin]

@nzardosh this change should address your issue with the wrong tables being joined with the embedding workflow, could you please import it and test that the inputs are set correctly?

[ktf]

Tested on hyperloop. Merging.