implement LoadInfo and ExtractInfo missing tracing

[rudolfix]

Background
We release a refactored tracing for 0.4.1 that unified the shapes of data across pipeline step. A few important features are still missing

Tasks

LoadInfo (after #757 )

1. • use improve destination fingerprinting and info #751 destination info to hold destination and staging infos, convert current fields to properties to keep the interface but not duplicate data
2. • dataset name may be different for each load_id so extend load info to keep this information
3. • remove elapsed from LoadJobInfo. Instead implement proper metrics for jobs generated in load.py. We should get start, stop times of the jobs initially. mind that you need to persist the metrics as this step is not atomic and may be restarted

ExtractInfo (after #754)

• • resource arguments (if created with decorator) - we have that partially implemented!
• • source arguments (if created with decorator) - to be implemented
    We should be careful what we send. Some of the arguments are secrets so initially we should only send arguments that are typed and not typed as secrets. for any other arguments we should just information that argument got set

Tests

1. • test trace generation LoadInfo for use_single_dataset pipeline setting which will generate separate dataset for each schema (we should move this config to load config or destination config)
2. • test persisted metrics in load. do they survive restarts?
3. • better ExtractInfo steps: we do not check the hints trace too well
4. • a proper test of the shape of the data: possibly using data contracts and pydantic (write a separate ticket!)