Read the Job and Project only from the bencher object

[epompeii]

The job callbacks branch now sends only the two-object dispatch payload, so the attach workflow reads the Job and the Project from the bencher object again and drops the fallback to the old top-level job and project keys. This restores the file as it was in #9.

[github-actions]

Bencher Report

Project	Example
Branch	u/ep/bare-metal-attach-payload
Testbed	ubuntu-latest

Click to view all benchmark results

Benchmark	Latency	Benchmark Result nanoseconds (ns) (Result Δ%)	Upper Boundary nanoseconds (ns) (Limit %)
bencher::mock_0	📈 view plot 🚷 view threshold	3.34 ns (-32.55%) Baseline: 4.96 ns	11.52 ns (29.02%)
bencher::mock_1	📈 view plot 🚷 view threshold	15.16 ns (-4.43%) Baseline: 15.86 ns	22.37 ns (67.76%)
bencher::mock_2	📈 view plot 🚷 view threshold	22.03 ns (-9.30%) Baseline: 24.29 ns	31.18 ns (70.67%)
bencher::mock_3	📈 view plot 🚷 view threshold	32.56 ns (-6.11%) Baseline: 34.68 ns	42.32 ns (76.93%)
bencher::mock_4	📈 view plot 🚷 view threshold	47.69 ns (+7.54%) Baseline: 44.35 ns	50.93 ns (93.65%)

🐰 View full continuous benchmarking report in Bencher

[github-actions]

Bencher Report

Project	Example
Branch	fork/u/ep/bare-metal-attach-payload
Testbed	ubuntu-latest

Click to view all benchmark results

Benchmark	Latency	Benchmark Result nanoseconds (ns) (Result Δ%)	Upper Boundary nanoseconds (ns) (Limit %)
bencher::mock_0	📈 view plot 🚷 view threshold	1.00 ns (-79.83%) Baseline: 4.96 ns	11.52 ns (8.68%)

🐰 View full continuous benchmarking report in Bencher