Feature Request: Make allowed file extensions configurable

[chrissonntag]

Hardcoded Allowed File Extensions Prevent Configuration Flexibility

Problem Description

The file processors for Fluid, TypoScript, Xml and Yaml in Fractor have hardcoded lists of allowed file extensions. This design prevents users from customizing which file extensions each processor should handle, limiting the tool's flexibility for projects with non-standard file naming conventions.

Root Cause

The allowedFileExtensions() methods in each of the following file processors return hardcoded arrays:

• FluidFileProcessor: ['html', 'xml', 'txt']
• TypoScriptFileProcessor: ['typoscript', 'tsconfig', 'ts']
• YamlFileProcessor: ['yaml', 'yml']
• XmlFileProcessor: ['xml']

These methods do not read from any configuration parameters, making the extensions immutable.

Expected Behavior

File processors should read allowed file extensions from respected configuration parameters, allowing users to customize them via Fractor's configuration system.

[simonschaufi]

This is almost a duplicate of #267

[chrissonntag]

Almost, right. But I think we can see #267 as a combination of this issue and #209 which I'm about to address with another PR in a few minutes. Both PRs combined would allow for a distinguished Fractor configuration that may solve the request of @d-s-codappix if I'm not mistaken.