improve auth capabilities for notification client and Swagger UI

[mgoetzegb]

What

• add: notifications - Allow authentication via Client Credentials flow (breaking change)

• change: make swagger docs compatible with access/authorization code flow

Why

We need to authenticate with client credentials in some scenarions.

Also Implicit auth flow is deprecated and should not be used. So we need the Swagger UI with access/authorization code flow.

References

ARTOSI-258

Checklist

• Tests

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Snapshot Warnings

⚠️: No snapshots were found for the head SHA acb8264.

Ensure that dependencies are being submitted on PR branches and consider enabling retry-on-snapshot-warnings. See the documentation for more information and troubleshooting advice.

Scanned Files

None

[github-actions]

Conventional Commits Report

Type	Number
Changed	1
Added	1

🚀 Conventional commits found.

[codecov]

Codecov Report

❌ Patch coverage is 28.00000% with 54 lines in your changes missing coverage. Please review.
✅ Project coverage is 56.59%. Comparing base (d0bd8a1) to head (acb8264).
⚠️ Report is 5 commits behind head on main.

Files with missing lines	Patch %	Lines
pkg/notifications/mocks/AuthClient.go	0.00%	41 Missing ⚠️
pkg/swagger/ginSwagger.go	0.00%	13 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #304      +/-   ##
==========================================
- Coverage   57.13%   56.59%   -0.55%     
==========================================
  Files          70       71       +1     
  Lines        3945     4006      +61     
==========================================
+ Hits         2254     2267      +13     
- Misses       1493     1543      +50     
+ Partials      198      196       -2     

Flag	Coverage Δ
opensearch-tests	95.68% <ø> (ø)
postgres-tests	92.03% <ø> (ø)
unit-tests	51.19% <28.00%> (-0.53%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[efernasier]

I'm not sure why govulncheck is failing. It seems doesn't like the way we are using testcontainers.

Maybe we may need a further ticket to move testcontainers usage out of the main library build.

Should we create a maintenance ticket?

[mgoetzegb]

I'm not sure why govulncheck is failing. It seems doesn't like the way we are using testcontainers.

Maybe we may need a further ticket to move testcontainers usage out of the main library build.

Should we create a maintenance ticket?

There is already a PR: #305 ;)