Use cycle-aware cache for GCP cloud metadata

**Motivation**

we currently initiate a cache in the GCP asset inventory provider to hold cloud account metadata:
https://github.com/elastic/cloudbeat/blob/ded46cab11e3966a0f9c3f15d0edc2f96b3c7219/internal/resources/providers/gcplib/inventory/provider.go#L178

but if the project/org names changed between cycles (unlikely, but possible) we'd still get the old values. we still need the cache itself, as resources tend to have same project/org names, but we need to make sure the values are fresh.

**Definition of done**
- [ ] make sure we get fresh values for cloud account metadata

**Related tasks/epics**
- raised in https://github.com/elastic/cloudbeat/pull/2055#discussion_r1568303037