fix(entities-plugins): mask key field in key auth mock schema used by consumer

[hangrao]

Summary

JIRA:KM-1839

Will generate entities-plugins pr package for testing.

[hangrao]

Tested manually:

1. cd apps/gateway-manager
2. pnpm install @kong-ui-public/entities-plugins@pr-2594
3. pnpm --filter "@kong-ui/konnect-ui-gateway-manager" dev

Go to consumer->credentials->Key Auth->Edit , the Key field is masked.

[sumimakito]

LGTM.

Note: I tested this in KM, but it didn't work. After some analysis, it turned out that KM fetches the backend schema for credentials and uses the schema there.

In today's backend schema, we're still missing the "encrypted": true (code reference). With that, we can also make the UI treat this field as a password.

Shall we reach out to the Gateway team and see if we need to add this field in the backend?

[hangrao]

LGTM.

Note: I tested this in KM, but it didn't work. After some analysis, it turned out that KM fetches the backend schema for credentials and uses the schema there.

In today's backend schema, we're still missing the "encrypted": true (code reference). With that, we can also make the UI treat this field as a password.

Shall we reach out to the Gateway team and see if we need to add this field in the backend?

Will review the KM part separately, this change is a nice to have change.

For KM, we'll update the fields for UI parts firstly, for backend related will consult PM and gateway team to see if they're going to update their part.