Fix/923 reduce the number of api

[Khadreal]

Description

Fixes #923
Reduce the number of times api is called.

Type of change

• Bug fix (non-breaking change which fixes an issue).

Detailed scenario

Check #923 for detailed scenario

Technical description

Documentation

Remove the api call from constructor and only call when it's needed.

Mandatory Checklist

Code validation

• I validated all the Acceptance Criteria. If possible, provide screenshots or videos.
• I triggered all changed lines of code at least once without new errors/warnings/notices.
• I implemented built-in tests to cover the new/changed code.

Code style

• I wrote a self-explanatory code about what it does.
• I protected entry points against unexpected inputs.
• I did not introduce unnecessary complexity.
• Output messages (errors, notices, logs) are explicit enough for users to understand the issue and are actionnable.

Unticked items justification

If some mandatory items are not relevant, explain why in this section.

Additional Checks

• In the case of complex code, I wrote comments to explain it.
• When possible, I prepared ways to observe the implemented system (logs, data, etc.).
• I added error handling logic when using functions that could throw errors (HTTP/API request, filesystem, etc.)

[jeawhanlee]

Good Job Sir!
This PR has only satisfied one part of the main issue, which is optimizing the way we call the API, however it does not cater for only loading those data on the bulk and settings screen as well as when the admin bar is hovered. See more details in the issue and AC here

[Mai-Saad]

Related test plan https://wpmediaqa.testrail.io/index.php?/runs/view/940&group_by=cases:section_id&group_order=asc

[Mai-Saad]

We have one test is failing (Note: in general, sometimes if other transients than imagify_user_cache is expired while we are doing test , API call may happen but after refresh no call) => failed test acceptable by @piotrbak
testrail-report-668.pdf