[core-data]: Fix TS types for user object

[manzoorwanijk]

This PR solves two issues

1. The core-data getCurrentUser selector's return type is set to ET.User< 'edit' >, which sets the incorrect return type with properties that don't exist on the current user object, for example, user.capabilities. The return type should rather be ET.User< 'view' > because that is what state.currentUser is, as mentioned in Convert core-data selectors from jsDoc annotations into TypeScript type signatures #40025 (comment)

Here, you can see the difference between a current user (users/me) and a normal user (users/<id>) object.

2. The type for user.capabilities is set to Record< string, string >, which is incorrect. It should rather be Record< string, boolean >, because those capabilities come from here as pointed out in Core Data: TypeScript definitions for entity records. #38666 (comment)

What?

• Fix the return type for getCurrentUser selector.
• Fix the type for user.capabilities to be a record of booleans instead of a record of strings.

Why?

To fix the incorrect types

How?

By fixing the types

Testing Instructions

• There is nothing really to test, you can just proof read and verify the behavior from REST API documentation.

Testing Instructions for Keyboard

Screenshots or screencast

Before	After

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: manzoorwanijk <manzoorwanijk@git.wordpress.org>
Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[github-actions]

Flaky tests detected in 8de2b23.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/17725084572
📝 Reported issues:

• [Flaky Test] ensures List View global shortcut works properly #51533 in /test/e2e/specs/editor/various/list-view.spec.js

[Mamaduka]

Sorry for the late reply, @manzoorwanijk!

The changes make sense. The REST API will use the default context view when the query argument isn't specified. The entities set the default context as part of baseURLParams, but that's not the case for the current user resolver.

https://github.com/WordPress/wordpress-develop/blob/dcc4c358f3bde4db290bb70665c14fe99cec23d1/src/wp-includes/rest-api/endpoints/class-wp-rest-users-controller.php#L125-L135