refactor(forges): read settings store inside the forge layer

[afonsojramos]

Summary

Split from #3034. Pushes the settings-store boundary into the forge layer:

• ForgeAdapter.listNotifications / enrichNotifications, both forge clients, and the notification-type handlers no longer thread a settings parameter through every call; they read useSettingsStore where the values are consumed.
• The handlers' universally unused _settings parameter is removed.
• Forge clients import the settings store leaf module directly (not the stores barrel), keeping the module graph free of a stores -> forges -> stores import cycle.
• Forge tests seed the settings store instead of passing settings objects.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
94.1% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud