feat!: remove cache durations for custom cache-control headers

[moritzraho]

Description

BREAKING CHANGE
Remove the following global level configuration entries:

• htmlcacheduration
• jscacheduration
• csscacheduration
• imagecacheduration

Note: we don't deprecated it as we want to favor custom cache-control headers under the correct web configuration category. see adobe/aio-lib-web#227 for more details

This also fixes warning logs that were sent to debugger.

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have signed the Adobe Open Source CLA.
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[shazron]

I'm wondering since this is a breaking change (thus a major) do we want to remove the two other deprecations in this release as well, maybe something we need to discuss.

[moritzraho]

I'm wondering since this is a breaking change (thus a major) do we want to remove the two other deprecations in this release as well, maybe something we need to discuss.

Good idea

Edit: after looking into it, some apps may still rely on the old configuration layout. We should (probably) gather some metrics first. Maybe we don't want to add an additional dependency for this release.

[purplecabbage]

const depValues = ['htmlCacheDuration', 'jsCacheDuration', 'cssCacheDuration', 'imageCacheDuration']
if (Object.keys(singleUserConfig).some(item => depValues.includes(item))) {...}

[purplecabbage]

Flagging as do-not-merge while we go through deprecation. #44 make an incremental step toward this.