Bug fixes

• Batch CMDB controls, such as AWS > Batch > Job Definition > CMDB, no longer nest a resource's AWS metadata (account ID, region, partition) inside itself during a mod upgrade. An affected resource lost its account ID and region, so its CMDB control looked it up in the wrong region; the CMDB controls now repair the resource in a single run. To find affected resources, filter on $.turbot.custom.aws.aws:!null and run their CMDB control. If that fails with an akas_aka_key error, or the resource stays nested, delete it — discovery keeps or re-creates the correct record.