Add analyser for OSGi config org.apache.sling.commons.log.LogManager.factory.config to always have file error.log

As other file names are not considered one should always point all custom loggers to `logs/error.log` (https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/debugging/debugging-aem-as-a-cloud-service/logs#custom-log-files). Although the check configuration analyser in https://github.com/apache/sling-org-apache-sling-feature-extension-apiregions/blob/master/src/main/java/org/apache/sling/feature/extension/apiregions/analyser/CheckConfigurationApi.java is suitable for this kind of check the property restriction (https://github.com/apache/sling-org-apache-sling-feature-extension-apiregions/blob/master/docs/api-regions.md#properties) is currently not outlined in the `factory-configurations` section of https://repo1.maven.org/maven2/com/adobe/aem/aem-sdk-api/2025.3.20133.20250325T063357Z-250300/aem-sdk-api-2025.3.20133.20250325T063357Z-250300-aem-publish-sdk.slingosgifeature

Start by reviewing the existing analyser entry points and CheckConfigurationApi.java, then compare the AEM SDK publish feature's factory-configurations section with the api-regions property restrictions documentation. The work is done when the analyser checks org.apache.sling.commons.log.LogManager.factory.config and flags custom logger configurations that do not use logs/error.log.

Written by the indexing model from the issue text.