feat: Integrate new Collage Designer and replace old Generator

[dasGOLE]

This commit introduces a new, dedicated Collage Designer, replacing the legacy collage generator. The goal is to provide a more flexible and robust platform for designing collages and also be able to move all collage settings in this designer in the future, laying the groundwork for future enhancements and a better user experience.

Prerequisites checklist

• I have read the contributing guidelines.

What is the purpose of this pull request? (put an "x" next to an item)

• Documentation update
• Bug fix
• New feature
• Other, please explain:

What changes did you make? (Give an overview)

Key changes include:

• Removal of Legacy Collage Generator: The old generator's entry points and related files have been removed or redirected. (Note: A dedicated cleanup commit for all generator-related files is planned for the future.)
• New Collage Designer Structure: A dedicated directory and file structure for the new Collage Designer (admin/collage-designer/) have been established to encapsulate its logic and assets.
• Initial Collage Designer Layout: The foundational HTML/CSS layout for the Collage Designer has been created, providing a basic UI for future design capabilities.
• Unified Configuration Rendering: The renderConfigManager was introduced and integrated into inputAdmin.php to standardize the rendering of configuration options across the admin panel, improving consistency and maintainability.
• Theme Renderer Adaptation: The theme renderer has been updated to utilize the new, general renderConfigManager, ensuring that theme-specific configurations are also processed through the unified rendering system.
• Enhanced Admin Panel Navigation:
  • The "Collage Designer" button in the admin panel now directly navigates to the new designer within the same tab, providing a smoother user flow.
• Optimized Admin Settings Save Logic:
  • A centralized saveAdminSettings() JavaScript function has been implemented for handling API requests to save admin configurations.
  • This function uses Promises for asynchronous handling and allows configurable behavior (e.g., page reload) via options.
  • An isDirty check (based on $('#save-admin-btn').hasClass('isDirty')) ensures that settings are only saved if actual changes have occurred, preventing unnecessary API calls and improving responsiveness.
  • The "Collage Designer" button now conditionally saves admin settings before navigation only if there are pending changes, otherwise, it navigates directly.
  • The main "Save" button in the admin panel retains its original behavior of reloading the page after saving.

Is there anything you'd like reviewers to focus on?

[reloxx13]

rebased and cs/ci fixes

[dasGOLE]

V1 of the designer reached.

I've been working on further features for the past few weeks, but since I haven't had time to reintegrate the back button or deal with the latest commits, it took a while to push the latest status. @reloxx13 I had to remove your commits regarding the removal of the back button and opening the designer in a new tab. Therefore, I adjusted the history and removed them.

However, I believe all fundamental functions required for the designer are now included. There are still a few design decisions on how certain things should be handled in the future:

Open "questions":

• How to handle orientation?
• Polaroid effect will not be implemented, nor will image filters... not needed, right? -> Maybe a note that these are only visible in testing?
• Drawing a cut line (4x...designes) -> should it be included in the JSON?
• Background image now adjustable per design, possibly with a fallback to config if none is set in the design settings (how to handle this in the frontend?)
• Frame now per design (regarding the single frame, should it be possible to select a different frame for each placeholder? Currently, the global one is selected, no individual selection possible)
• CSS for the tools buttons (top) could be improved (hover, pressed states)

Currently, the designer requires the following JSON structure, for example:

{
"name": "1+2 Layout",
"author": "PhotoboothProject",
"aspect_ratio": "3:2",
"width": "1800",
"height": "1200",
"background": null,

"background_color": "#FFFFFF",

"elements": [
{
"type": "image",
"id": "img-0",
"x": "0",
"y": "y0.055",
"width": "x0.55546",
"height": "y0.55546",
"rotation": "10",
"show_frame": true,

"src": "resources/img/demo/seal-station-norddeich-02.jpg"

},
{
"type": "image",
"id": "img-1",
"x": "x0.555",
"y": "y0.055",
"width": "x0.40812",
"height": "y0.40812",
"rotation": "0",
"show_frame": false,
"src": null
},
{
"type": "image",
"id": "img-2",
"x": "x0.555",
"y": "y0.5368",
"width": "x0.40812",
"height": "y0.40812",
"rotation": "0",
"show_frame": false,
"src": null
},
{
"type": "text",
"id": "txt-0",
"x": "x0.5",
"y": "y0.5",
"width": "x0.3",
"height": "y*0.1",
"rotation": "30",
"content": "I'm a Test",
"font_family": "resources/fonts/GreatVibes-Regular.ttf",
"font_color": "#000000",
"font_size": 20,
"text_horizontal_align": "center",
"text_vertical_align": "center",
"font_bold": false,
"font_italic": false,
"font_underline": false
}
]
}

The new JSON structure could also store the background image, the single frame, and it might be possible to set a custom/different frame for each placeholder (this would then need to be supplemented in the JSON structure and the designer).
Therefore, it could look like this:

New JSON:
{
"width": "1800",
"height": "1200",
"background": "/resources/img/background.png",
"background_color": "#FFFFFF",
"frame": "resources/img/frames/frame.png",
"show_frame": true,
"elements": [ // NEW: Unified array for all elements
{
"type": "image",
"id": "img-1",
"x": "0", "y": "y * 0.055", "width": "1.5 * y * 0.55546", "height": "y * 0.55546", "rotation": "10",
"apply_frame": true,
"src": "placeholder.png" // Could be a generic placeholder or empty for backend to fill
},
{
"type": "text",
"id": "txt-line1",
"x": "200", "y": "220", "width": "300", "height": "50", "rotation": "10",
"content": "This is",
"font_family": "/resources/fonts/GreatVibes-Regular.ttf",
"font_color": "#420C09",
"font_size": "50",
"text_align": "center"
}
// ... more elements ...
]
}

Currently, the designer is not functional due to conflicts with CollageLayoutEnum. Additionally, a rebase onto the current dev branch would be necessary, but I would wait until "Allow custom collage layouts from private folder #1428" is merged, as this would also resolve the errors related to CollageLayoutEnum.

I'm eager for your feedback, and if this looks good, we could now proceed to the backend and the migration to the new JSON structure. :)