ACM-28831 Disable AppSet auto sync when the option is unchecked

[fxiang1]

📝 Summary

Ticket Summary (Title):
Implement option to disable AppSet autosync completely

• Grouped all automated sync related checkboxes into a separate section
• Introduced a new Enable automated sync checkbox which will disable all other settings when unchecked
• Added tooltip to let user know settings will be ignored when automated sync is disabled
• Checking Enable automated sync will enabled the other settings again
• Supports old automated sync behavior when syncPolicy.automated exists but no enabled field. This will add enabled=true by default.

Ticket Link:
https://issues.redhat.com/browse/ACM-28831

Type of Change:

• 🐞 Bug Fix
• ✨ Feature
• 🔧 Refactor
• 💸 Tech Debt
• 🧪 Test-related
• 📄 Docs

---

✅ Checklist

General

• PR title follows the convention (e.g. ACM-12340 Fix bug with...)
• Code builds and runs locally without errors
• No console logs, commented-out code, or unnecessary files
• All commits are meaningful and well-labeled
• All new display strings are externalized for localization (English only)
• (Nice to have) JSDoc comments added for new functions and interfaces

If Feature

• UI/UX reviewed (if applicable)
• All acceptance criteria met
• Unit test coverage added or updated
• Relevant documentation or comments included

If Bugfix

• Root cause and fix summary are documented in the ticket (for future reference / errata)
• Fix tested thoroughly and resolves the issue
• Test(s) added to prevent regression

---

🗒️ Notes for Reviewers

[fxiang1]

/retest

[KevinFCormier]

/hold

[KevinFCormier]

Hey Feng. The behaviour seems a little strange to me.

• "Automatically sync when cluster state changes" corresponds to selfHeal, but when it is not checked, would it be equivalent if we set the other 2 options under automated (prune and allowEmpty) to false as well, rather than nulling it out?
• Should we re-order the checkboxes to show the relationship between this one and the other two that become disabled?
• When I loaded an application where the "automated" section had been removed for editing, the 2 checkboxes were not disabled.

There was also a stray macOS file checked in that should be removed.

[KevinFCormier]

Please remove this file. I see it is gitignored for frontend, but you could add the ignore at the root level instead.

[fxiang1]

Hey Feng. The behaviour seems a little strange to me.

* "Automatically sync when cluster state changes" corresponds to selfHeal, but when it is not checked, would it be equivalent if we set the other 2 options under automated (prune and allowEmpty) to false as well, rather than nulling it out?

* Should we re-order the checkboxes to show the relationship between this one and the other two that become disabled?

* When I loaded an application where the "automated" section had been removed for editing, the 2 checkboxes were not disabled.

There was also a stray macOS file checked in that should be removed.

Thanks Kevin! The changes for these comments are done.

[KevinFCormier]

/lgtm

[KevinFCormier]

/unhold

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fxiang1, KevinFCormier

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [KevinFCormier,fxiang1]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
83.3% Coverage on New Code
0.9% Duplication on New Code

See analysis details on SonarQube Cloud