"Corrupted" permissions aren't showing correctly on the FE

**Describe the bug**
A weird case where, if you change the permissions graph via the API, then the FE doesn't show the values correctly.

**Logs**
NA

**To Reproduce**
On a brand new Metabase:
1) go to /admin/permissions/data/group
2) click on "All users" to see the permissions that the group has. Default should be:
3) Now Block data access to "All users", so you will have the permissions like:
4) Now go to /admin/people/groups and create a new group, then go back to permissions and block the data access to this new group
5) Now using the tool you like to a PUT request to /api/permissions/graph, with the following payload
{"groups":{"1":{"3":{"download": {"native": "full", "schemas": "full"}, "data": {"schemas": "block"}}},"2":{"3":{"data":{"native":"write","schemas":"all"},"download":{"native":"full","schemas":"full"},"data-model":{"schemas":"all"},"details":"yes"}},"3":{"3":{"data":{"native":"none","schemas":"block"}}}},"revision":2}
6) Now refresh the page, you'll see that the page has an alert that the All users group is more permissive, but according to the UI, it isn't:


**Expected behavior**
Show the correct message on the FE (Download results: YES)

**Screenshots**
Above

**Information about your Metabase Installation:**
- Your browser and the version: Brave latest
- Your operating system: Pop-OS 22.04
- Your databases: H2
- Metabase version: 1.43.4
- Metabase hosting environment: Docker
- Metabase internal database: Postgres 14.2

**Severity**
Cosmetic

**Additional context**
Workaround: set the group to another data permission, and then revert back, so the frontend does the correct API requests to remove the permissions

Reproduce the issue from /admin/permissions/data/group using the PUT /api/permissions/graph payload in the report, then trace how the permissions graph is rendered in the frontend. Done means the UI shows the correct alert and “Download results: YES” after the API changes, including the supplied reproduction sequence.

Written by the indexing model from the issue text.