Fix Issue #2782 - Resolve GeeksForGeeks False Positives

[MaxwellOldshein]

This PR corrects the false positive issue for the GeeksForGeeks site as stated in: #2782. This was due to the fact that there is no longer a reliable way to check valid vs. invalid usernames for the GeeksForGeeks site, which previously leveraged the status_code detection methodology when it was working before.

Known Valid Username Behavior --> adam:

curl -Ls -o /dev/null -w '%{http_code} %{url_effective}\n' 'https://auth.geeksforgeeks.org/user/adam'

# 200 https://auth.geeksforgeeks.org/profile/adam

curl -Ls 'https://auth.geeksforgeeks.org/user/adam' | grep -o '404 Not Found' || echo 'NO MATCH'

# 404 Not Found

Known Invalid Username Behavior --> thisisatotallyfakeusername123456:

curl -Ls -o /dev/null -w '%{http_code} %{url_effective}\n' 'https://auth.geeksforgeeks.org/user/thisisatotallyfakeusername123456'

# 200 https://auth.geeksforgeeks.org/profile/thisisatotallyfakeusername123456

curl -Ls 'https://auth.geeksforgeeks.org/user/thisisatotallyfakeusername123456' | grep -o '404 Not Found' || echo 'NO MATCH'

# 404 Not Found

Closes #2782.