Better check for WPCOMness

[andres-blanco]

In the old credentials flow we were checking for WPCOMness based on the points_to_wpcom_servers function (fbhepr%2Skers%2Sjcpbz%2Snflap%2Qwbof%2Svapyhqrf%2Szvtengvba%2Snhgbzngrq%2Qzvtengvba.cuc%3Se%3Q0s050q9q%23116-og). In the AP flow we started relying on the analysis endpoint. This should change, since the points_to_wpcom_servers function is better at telling if a site is already on DOTCOM.

Action items

• Verify where should this check go in the AP flow. To do this, the first step would be to add the check somewhere in this method: fbhepr%2Skers%2Sjcpbz%2Snflap%2Qwbof%2Svapyhqrf%2Szvtengvba%2Snhgbzngrq%2Qzvtengvba.cuc%3Se%3Q0s050q9q%23831-og and log when this case happens
• Monitor the logs for the previously added entry
• If it's common, then we need to figure out how to check before getting to the automated_migration_process_application_passwords job and redirect to the poll step. But we will cross that bridge if we need to.

[github-actions]

OpenAI suggested the following labels for this issue:

• [Feature Group] Other Infrastructure: The issue relates to improving an internal infrastructure check for the async job, suggesting a focus on backend processes.
• [Feature] API: The mention of the 'points_to_wpcom_servers' function indicates using an API for server communications in async jobs.
• [Feature] Plugins: Since the function is used in conjunction with a prior credential flow job, it suggests integration with plugins to manage functionality.