udpdate mocks for `conf.kri`

[johncowen]

Kuma Version

2.13.x

Describe the bug

During #4578 we updated the policy origins to display differently. We could only do this because the conf for each policy now includes the kri (conf.kri)

I noticed that the mocks for the endpoint we use for this information does not ever have conf.kri set and thus during development using mocks we see Policy Origin: <blank>

We should update the mocks so that it does.

I think this is the mock

kuma-gui/packages/kuma-http-api/mocks/src/meshes/_/dataplanes/_/_inbounds/_/_policies.ts

Line 19 in 41874f3

conf: (() => {

To Reproduce

No response

Expected behavior

No response

Additional context (optional)

No response

[schogges]

Yes, we are missing a mock KRI here, but not in conf. The KRIs are at the same level as conf:

conf: {...},
kri: ...

so we have to add a mock KRI to policies[].rules[].kri.
Also relevant for this is that policies[].origins[] is a list of unique KRIs of the policies that are affecting the inbound with their rules. So a KRI that is listed under policies[].origins[].kri can be reused for policies[].rules[].kri. In #4578 we've basically replaced using policies[].origins[].kri with policies[].rules[].kri such that we don't show all the policies[].origins[].kri per each policies[].rules[].

[johncowen]

Sorry yeah not totally sure where its wrong tbh, but somewhere a kri is missing in that mock