fix: added correct api endpoint for verification & logic for Aeroworkflow

[sahil9001]

Description:

Fixes #3434 .

API Endpoint Correction:

• Current: The detector uses /api/{accountid}/v1/AeroAppointments for verification.
• Issue: This endpoint is not appropriate as it might involve COGs.
• Fix: Update to use /api/{accountid}/me, which aligns with other detector patterns.
• Reference: https://api.aeroworkflow.com/swagger/index.html

Checklist:

• Tests passing (make test-community)?
• Lint passing (make lint this requires golangci-lint)?

[sahil9001]

@rgmz

[zricethezav]

Issue: This endpoint is not appropriate as it might involve COGs.

Can you elaborate on this? I'm not familiar with COGs

[sahil9001]

Issue: This endpoint is not appropriate as it might involve COGs.

Can you elaborate on this? I'm not familiar with COGs

In this scenario, "COGs" is referring to sensitive or privileged information related to customer-owned items or data. The concern seems to be that the current endpoint (/api/{accountid}/v1/AeroAppointments) might be accessing or exposing information about customer-owned goods or property, which could be a privacy or security issue.

By switching to the /api/{accountid}/me endpoint, the system would likely be accessing only user-specific information rather than potentially sensitive customer-owned data. This change aligns better with standard practices for user verification and reduces the risk of inappropriately handling customer-owned information.