feat(ui): rename filter message status on SYNC STATUS view

[aali309]

Original PR: #20850

Description

Rename configured filter to changed in the SYNC STATUS view to make it more self-explanatory for users. This helps users clearly distinguish between resources that were changed and those that remained untouched during sync.

Changes

• Renamed configured to changed in FilterableMessageStatuses
• No functional changes to the filtering logic

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
• The title of the PR states what changed and the related issues number (used for the release note).
• The title of the PR conforms to the Toolchain Guide
• I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
• I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
• Does this PR require documentation updates?
• I've updated documentation as required by this PR.
• I have signed off all my commits as required by DCO
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My build is green (troubleshooting builds).
• My new feature complies with the feature status guidelines.
• I have added a brief description of why this PR is necessary and/or what this PR solves.
• Optional. My organization is added to USERS.md.
• Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).

[bunnyshell]

❌ Preview Environment deleted from Bunnyshell

Available commands (reply to this comment):

• 🚀 /bns:deploy to deploy the environment

[aali309]

[anandf]

LGTM

[keithchong]

If these do not represent the actual text we are searching for, then perhaps we should capitalize the first letter:
['Changed', 'Unchanged']

Also, this will make it consistent with the other three existing filters.

[keithchong]

Also, maybe we can add a tooltip like this, to explain it, and users won't get confused.

Here's the code for it:

<Tooltip
    placement='top-start'
    content={<div>Filter on resources that have changed or remained unchanged</div>}>
    <div>
        <Filter options={FilterableMessageStatuses} filters={messageFilters} setFilters={setMessageFilters} title='MESSAGE'/>
    </div>
</Tooltip>

Maybe @jannfis can finalize on the wording?

[aali309]

Also, maybe we can add a tooltip like this, to explain it, and users won't get confused.

Here's the code for it:

<Tooltip
    placement='top-start'
    content={<div>Filter on resources that have changed or remained unchanged</div>}>
    <div>
        <Filter options={FilterableMessageStatuses} filters={messageFilters} setFilters={setMessageFilters} title='MESSAGE'/>
    </div>
</Tooltip>

Maybe @jannfis can finalize on the wording?

@keithchong, out of the 4, this will be the only item with a tooltip, a little bit inconsistent may be? If we add to all then that should be on a different PR?

[keithchong]

@aali309, I think it is fine since the others are more self-explanatory.

[keithchong]

LGTM