Task/update typo3 template jan 2024

What does this MR do and why?

Add latest changes of the TYPO3 project template

• [TASK] Better error handling for typo3-init command
• [TASK] Require typo3/cms-lowlevel as dev dependency
• [FEATURE] Add configuration for a sitemap.xml
• [TASK] Clean up templating
• [FEATURE] Add configuration and data for a 404 page
• [TASK] Configure CronJob for EXT:scheduler
• [BUGFIX] Import SCSS for rte directly
• [TASK] Ignore labels locally, download on deployment
• [TASK] Add more information regarding ddev to the README

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Hey @ochorocho!

Thank you for your contribution to GitLab. Please refer to the contribution documentation for an overview of the process.

When you're ready for a first review, post @gitlab-bot ready. If you know a relevant reviewer(s) (for example, someone that was involved in a related issue), you can also assign them directly with @gitlab-bot ready @user1 @user2.

At any time, if you need help, feel free to post @gitlab-bot help or initiate a mentor session on Discord. Read more on how to get help.

You can comment @gitlab-bot label <label1> <label2> to add labels to your MR. Please see the list of allowed labels in the label command documentation.

This message was generated automatically. You're welcome to improve it.

added Community contribution workflowin dev labels

assigned to @ochorocho

@gitlab-bot ready @vyaklushin

added workflowready for review label and removed workflowin dev label

requested review from @vyaklushin

@vyaklushin, this Community contribution is ready for review.

• Do you have capacity and domain expertise to review this? If not, find one or more reviewers and assign to them.
• If you've reviewed it, add the workflowin dev label if these changes need more work before the next review.

This message was generated automatically. You're welcome to improve it.

	2 Warnings
	This merge request does not refer to an existing milestone.
	Labels missing: please ask a reviewer or maintainer to add backend to this merge request.

	1 Message
	CHANGELOG missing: If this merge request needs a changelog entry, add the Changelog trailer to the commit message you want to add to the changelog. If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.

Reviewer roulette

Changes that require review have been detected!

Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:

Category	Reviewer	Maintainer
backend	@hustewart (UTC-5)	@bmarjanovic (UTC+1)

Please check reviewer's status!

• Reviewer is available!
• Reviewer is unavailable!

Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.

To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.

Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

mentioned in issue gitlab-org/quality/triage-reports#15807 (closed)

changed milestone to %16.10

added Category:Source Code Management Category:Templates featureenhancement labels

added typefeature label

added groupsource code label

added devopscreate sectiondev labels

changed milestone to %16.9

added backend label

approved this merge request

Thank you for the contribution!

LGTM

@vyaklushin, thanks for approving this merge request.

This is the first time the merge request has been approved. To ensure we don't only run predictive pipelines, and we don't break master, please start a new pipeline before merging.

Please wait for the pipeline to start before resolving this discussion and set auto-merge for the new pipeline. See merging a merge request for more details.

added pipeline:mr-approved label