fix: added http status code to cache and caching response

[ResuBaka]

Short Description and Why It's Useful

Currently the http code from a response is not cached and it should as 404 pages can be cached to. The 404 is only an example of status codes that may be cached or are wanted to be cached.

Screenshots of Visual Changes before/after (if There Are Any)

Which Environment This Relates To

Check your case. In case of any doubts please read about Release Cycle

• Test version (https://test.storefrontcloud.io) - this is a new feature or improvement for Vue Storefront. I've created branch from develop branch and want to merge it back to develop
• RC version (https://next.storefrontcloud.io) - this is a stabilisation fix for Release Candidate of Vue Storefront. I've created branch from release branch and want to merge it back to release
• Stable version (https://demo.storefrontcloud.io) - this is an important fix for current stable version. I've created branch from hotfix or master branch and want to merge it back to hotfix

Upgrade Notes and Changelog

• No upgrade steps required (100% backward compatibility and no breaking changes)
• I've updated the Upgrade notes and Changelog on how to port existing Vue Storefront sites with this new feature

IMPORTANT NOTICE - Remember to update CHANGELOG.md with description of your change

Contribution and Currently Important Rules Acceptance

• I read and followed contribution rules

[pkarw]

To be ported into VSF 1.11 as well

[ResuBaka]

Do you guys want to add the changelog entry or should I do it?

[pkarw]

Yes, please

[ResuBaka]

Done @pkarw

And changed to merge into the hotfix branch. Most of the changes you can see in here are coming from the master as my branch is based on the master.

[andrzejewsky]

@ResuBaka I think you have to rebase with the source branch, or cherry-pick your commits

[ResuBaka]

I have fixed it :)

Force push + cherry-pick = 🔥