Update blacklisted paths to support new CSS/JS aggregate method introduced in Drupal 10.1

Updated the default installation variable. However, we might need to create an update hook for existing module users to streamline update to Drupal 10.1+

I'm not sure how the upgrade path should be but I feel this should be merged to avoid new installations without the path that should be ignored. The upgrade path can be managed in a followup.

The upgrade patch is not that hard. You need to fetch the config, loop over the blacklisted_paths, check for existence and add when not found.
But ... Not every site is installed in the default folder. So maybe the documentation should be updated to include this change?

But it does fix the aggregation problem. So good to have this as default behavior.

Automatically closed - issue fixed for 2 weeks with no activity.