feat(core): implement SecurityIntegration ENABLED filter.

[ammeek]

✨ Description

What does this PR change?
Add SecurityIntegration ENABLED filter

🔗 Related Issue

relates to kestra-io/kestra-ee#6256

🛠️ Backend Checklist

• Code compiles successfully and passes all checks
• All unit and integration tests pass

[github-actions]

🐋 Docker image

ghcr.io/kestra-io/kestra-pr:14839

docker run --pull=always --rm -it -p 8080:8080 --user=root -v /var/run/docker.sock:/var/run/docker.sock -v /tmp:/tmp ghcr.io/kestra-io/kestra-pr:14839 server local

🧪 Java Unit Tests

	Tests	Passed ✅	Skipped ⚠️	Failed	Time ⏱
Java Tests Report	4055 ran	4042 ✅	13 ⚠️	0 ❌	43m 12s 413ms

[github-actions]

Tests report quick summary:

success ✅ > tests: 4055, success: 4042, skipped: 13, failed: 0

unfold for details

Project	Status	Success	Skipped	Failed
cli	success ✅	80	0	0
core	success ✅	2003	0	0
executor	success ✅	4	0	0
jdbc	success ✅	11	0	0
jdbc-h2	success ✅	473	0	0
jdbc-mysql	success ✅	476	0	0
jdbc-postgres	success ✅	476	0	0
processor	success ✅	7	0	0
runner-memory	success ✅	1	0	0
scheduler	success ✅	23	0	0
script	success ✅	12	0	0
storage-local	success ✅	64	0	0
webserver	success ✅	421	0	0
worker	success ✅	4	0	0

---

Develocity build scan: https://develocity.kestra.io/s/ylrmq4ent7ktg

[AcevedoR]

shouldnt SECURITY_INTEGRATION be present in the openapi spec ?

[ammeek]

shouldnt SECURITY_INTEGRATION be present in the openapi spec ?

Yea it should be, will regenerate the openapi spec.

[ammeek]

@AcevedoR As mentioned here SECURITY_INTEGRATION should not be in the open api spec file.

[nkwiatkowski]

LGTM