DPL Analysis: use Input/OutputSpec metadata to detect special tables instead of origins

[aalkin]

• Populate OutputSpec for spawned or index table with corresponding metadata, similar to the one present in InputSpec for the same table
• Use the presence of these metadata entries to form the inputs list for the aod-spawner and index-builder

Previously, special origins DYN/IDX were used to identify spawned and index tables. With embedding in mind, we will need to distinguish between the spawned and index tables coming from different file sources, meaning we can no longer rely on origins. This change moves the logic to metadata inspection, that permits us to free the origins for their original purpose - determining the source of data.

[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