Improve GraphQL lazy abstractions

What does this MR do?

This improves some of our GraphQL lazy abstractions by:

• having our lazy aggregates all support a common interface (which makes elimination simpler)
• adding asynchronous catch, to deal with errors

As a developer-facing tooling change, this does not require a Changelog entry.

This MR was extracted from, and supports, !40088 (merged)

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team