Filter with authData "key does not exist" shows incorrect results

New Issue Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.
• I can reproduce the issue with the latest versions of Parse Server and Parse Dashboard.

Issue Description

When setting a data browser filter on field authData, condition key does not exist, value facebook, it shows records that contain auth data with key facebook, but with the authData field empty. That means, not only does it show the records even though it should not show them, the record itself is incorrect as it has an empty authData field which is not the case.

Steps to reproduce

Given the following records in _User:

• objectId: a, authData: (empty)
• objectId: b, authData: { 'facebook': ...}

Filter condition key does not exist, value facebook shows:

• objectId: a, authData: (empty)
• objectId: b, authData: (empty)

but it should show:

• objectId: a, authData: (empty)

Environment

Dashboard

• Parse Dashboard version: 6.0.0-alpha.11

Start by reproducing the issue in the data browser with the two _User records and the authData filter described. Trace how the key does not exist condition is applied and how the returned authData values are displayed. Done means only object a appears and its empty authData remains accurate.