Added 2 new request attribute mappings for TYPO3 v13

[derhansen]

• Added frontend.page.information - see https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ApiOverview/RequestLifeCycle/RequestAttributes/FrontendPageInformation.html#frontend-page-information

• Added frontend.cache.instruction - see https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ApiOverview/RequestLifeCycle/RequestAttributes/FrontendCacheInstruction.html#frontend-cache-instruction

[sascha-egerer]

We still need a way to make this TYPO3 version dependent as these types are now also valid in older TYPO3 versions with the current implementation.

[derhansen]

Can you elaborate what this means for this PR? Should we have different versions of the package for different TYPO3 versions or make requestGetAttributeMapping somehow TYPO3 major version aware? IMO, it would be fine to just add the types as is, since they just provide type mapping for the static code analysis and I doubt developers will use v13 only request attributes in <v13 projects.

But I'm also fine to just add the mapping to my custom phpstan.neon file :-)

[sascha-egerer]

I'm not yet sure how to solve the issue with supporting multiple TYPO3 versions. We do also have issues with the stubs where we already have a way to load them based on the TYPO3 version. But we really have to clean this up. I'll try to have a look at it soon.

[sascha-egerer]

@derhansen I've merged #176 and did not notice that this is also part of your PR. So i wanted to rebase your's now and merge it but i'm not able to push into your PR. Could you please rebase remove the duplicate frontend.page.information?
Thank you.

[derhansen]

@derhansen I've merged #176 and did not notice that this is also part of your PR. So i wanted to rebase your's now and merge it but i'm not able to push into your PR. Could you please rebase remove the duplicate frontend.page.information? Thank you.

Done