Support versionNumberInFilename in TYPO3 nginx configuration

[codemonkey1988]

Is your feature request related to a problem? Please describe.
TYPO3 can be configured to add a version number to every asset. You need to set

['BE']['versionNumberInFilename'] = '1'
['FE']['versionNumberInFilename'] = 'embed'

in typo3conf/LocalConfiguration.php
TYPO3 generates assets like typo3temp/assets/compressed/ext-all-notheme-2eace0db537855958e1f9336373b0fff.1531244432.css
The original asset is located at typo3temp/assets/compressed/ext-all-notheme-2eace0db537855958e1f9336373b0fff.css

Describe the solution you'd like
There needs to be a nginx rule to resolve the asset paths to the correct location. The corresponding htaccess rule is

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.+)\.(\d+)\.(php|js|css|png|jpg|gif|gzip)$ $1.$3 [L]

Describe alternatives you've considered
The current solution is to disable these settings by setting

['BE']['versionNumberInFilename'] = '0'
['FE']['versionNumberInFilename'] = ''

Additional context
Can be reproduced in TYPO3 7, 8 and 9. Just set the described setting and call the TYPO3 backend login form. All css is missing without an additional nginx configuration because the css files can not be resolved.

[rfay]

Currently ddev doesn't touch LocalConfiguration.php, but creates AdditionalConfiguration.php - I assume this can be handled there?

A PR is to the AdditionalConfiguration.php is welcome on this, I'm not sure at this point I completely understand how to resolve it.

[codemonkey1988]

The best solution would be to translate the given htaccess rule to nginx configuration and put it into the nginx TYPO3 config file. Then it will work either the configuration is set or not. I will try do to this, but I don't have any experience with nginx config. Maybe someone with nginx configuration knowhow can help here?