Closes #7038 Activate minification by default

[Khadreal]

Description

Fixes #7038
Activate minification by default.

Type of change

• Enhancement (non-breaking change which improves an existing functionality).

Detailed scenario

Check EPIC Card

Technical description

Change the value of minify_css/js to 1 to activate it by default.

Documentation

Mandatory Checklist

Code validation

• I validated all the Acceptance Criteria. If possible, provide screenshots or videos.
• I triggered all changed lines of code at least once without new errors/warnings/notices.
• I implemented built-in tests to cover the new/changed code.

Code style

• I wrote a self-explanatory code about what it does.
• I protected entry points against unexpected inputs.
• I did not introduce unnecessary complexity.

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
Report missing for 815e6391	✅ 100.00% (target: 50.00%)

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (815e639)	Report Missing	Report Missing	Report Missing
Head commit (b534476)	37750	16597	43.97%

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#7052)	4	4	100.00%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

_{Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more}

Footnotes

1. Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct. ↩

[Miraeld]

I'm approving the change as it's ok for me. However,
This is a 3.18 feature, should we merge it onto develop or a 3.18 branch ?

[remyperona]

We should create a branch-3.18 and merge it in it for now

[Miraeld]

Created a feature/3.18 branch and rebased this PR on it :)