MCS-API API change feedbacks on `endpointSliceObjects`

Hi 👋,

I am reaching out on behalf of SIG Multicluster as you are listed as a MCS-API implementations here https://multicluster.sigs.k8s.io/implementations/mcs-implementations/.

This is related to this MCS-API KEP change https://github.com/kubernetes/enhancements/pull/6037 that would requires implementations to add a new field called `endpointSliceObjects` to the ServiceImport status (currently with two possible value `Present`/`Absent`). This change the conformance expectation so we are reaching out for feedbacks but is non breaking (nothing will break if you were to not do that). Note that as it's still a simple change we have set a lazy consensus of 2 weeks to get feedbacks on this.

Additionally in case you are interested by upstream MCS-API change it could be useful to provide some github handle so that we can ping you on some MCS-API discussions where some implementations feedbacks may be useful or to inform you of some changes. Note that we usually announce important change on the SIG mailing list and would encourage to subscribe if not already done (it's very low volume, like maybe a maximum of ~5-10 mails a year usually).

Read the linked MCS-API KEP change in enhancements PR 6037 and inspect how this controller represents ServiceImport status and endpoint slices. Determine whether the proposed endpointSliceObjects Present/Absent status is supported, then provide implementation feedback or a maintainer contact; the issue is done when SIG Multicluster has a clear response.

Written by the indexing model from the issue text.