CR-3530 Fix for AME-3528: Mention CORS support in OpenAM release notes

In fact, as David Luna pointed out in the review, CORS support requires additional configuration in the deployment descriptor. So this patch also adds instructions to help with that, as reviewed. Those instructions are still likely to be useful, even if we include the configuration commented out in the default deployment descriptor file.

git-svn-id: https://svn.forgerock.org/openam/trunk@8987 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
OpenAM-3896, CR-3546 - Default entitlements web application resource patterns are too restrictive

git-svn-id: https://svn.forgerock.org/openam/trunk@8988 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
OPENAM-3569, FR-184 - Update web.xml to include example configuration for CORS Filter

git-svn-id: https://svn.forgerock.org/openam/trunk@8989 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
OPENAM-3984, CR-3549 - Resolved ClientSDK deployment issue through bypass of Guice constructors in non-server mode

git-svn-id: https://svn.forgerock.org/openam/trunk@8991 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
Typo

git-svn-id: https://svn.forgerock.org/openam/trunk@8993 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d
Editorial: align organization of the older policy management section with the new, and update the section titles to align with others in the chapter

git-svn-id: https://svn.forgerock.org/openam/trunk@8997 0f4defcf-c51a-4c67-9f44-6fb5eba73c5d