Fix | Make plugin VIP compliant by removing usage of wp_remote_get

[sksaju]

Description of the Change

This update replaces all usages of wp_remote_get with the vip_safe_wp_remote_get function to ensure compatibility with WordPress VIP coding standards and improve overall security and reliability when making HTTP requests.

Closes #791

How to test the Change

• Checkout this branch.
• Navigate to any feature or function in the plugin that previously relied on wp_remote_get for making external requests.
• Verify that requests are now handled via vip_safe_wp_remote_get.
• Confirm expected data is returned and no errors or regressions occur.
• If applicable, test with error handling (e.g., simulate timeouts or invalid URLs) to ensure graceful fallback or logging.

Changelog Entry

• Replaced all usage of wp_remote_get with vip_safe_wp_remote_get for VIP compliance.
• Ensured all affected requests handle timeouts and response validation correctly.
• Minor code cleanup related to the refactored HTTP requests.

Checklist:

• I agree to follow this project's Code of Conduct.
• I have updated the documentation accordingly.
• I have added Critical Flows, Test Cases, and/or End-to-End Tests to cover my change.
• All new and existing tests pass.

[dkotter]

So previously we were setting a higher timeout value here to give the request longer to succeed. That is now removed and I think we'll want to add that back.

[sksaju]

@dkotter we have that value in the helper function here

classifai/includes/Classifai/Helpers.php

Line 698 in 128c517

'timeout' => 20, // phpcs:ignore

[dkotter]

@sksaju Apologies, merged this in but didn't realize this was raised against feature/azure-language-service and not develop. I'm assuming the reasoning here is that PR added in the safe_wp_remote_get function that we wanted to use here. I'm not sure when/if we'll get that other PR merged in so would be ideal if we can get a PR opened against develop and not based off of feature/azure-language-service so we can get this released

[jeffpaul]

Would also be nice to consider splitting out the VIPCS from https://github.com/10up/classifai/blob/develop/.github/workflows/phpcs.yml into specific YML for https://github.com/10up/wpcs-action/ that's VIPCS only so we can add that check and a related readme badge to note ClassifAI is passing VIPCS?

[av3nger]

@jeffpaul, I've created a separate with a single missing fix: #987
Also, the VIP standards action is already implemented on https://github.com/10up/classifai/actions/workflows/vipcs.yml