[M108 Migration] Add back MaybeCheckCSP() method which was removed in upstream
In M63, MaybeCheckCSP() method was used to decide navigation policy
by checking CSP rules. After M63, the method was removed in upstream
patches [1] & [2] which caused the navigation policy to be decided
by ContentRendererClient. For WebApps, it is routed to WRTRenderClient.
In WRT, the navigation policy is decided but also requests app_control
to the refused URL to support backward compatibility which can't be
avoided, thus resulting in unexpected launch of VD Browser.
[1] https://chromium-review.googlesource.com/c/chromium/src/+/1037804
[2] https://chromium-review.googlesource.com/c/chromium/src/+/1083825
This patch adds back MaybeCheckCSP() to decide the policy at blink side
itself, so that the request doesn't reach WRT.
References:
https://review.tizen.org/gerrit/279285
Change-Id: I32ee8fe2f1d833aa945fa1ab9b5e86b7a179f372
Signed-off-by: v-saha <v.saha@samsung.com>