Enable ScriptForbiddenScope in release builds

In order to make sure that we don't execute a script where script execution is forbidden, it is important to get a stack trace of the exact code path that violates the condition in release builds. Then we can fix the code path.

I want to make this change because recently I've observed a couple of crashes probably caused by a script being executed in a ScriptForbiddenScope (e.g., weak callback of V8 GC, weak processing of Oilpan GC).

BUG=389445

Review URL: https://codereview.chromium.org/381493003

git-svn-id: svn://svn.chromium.org/blink/trunk@178351 bbb929c8-8fbe-4397-9dbb-9b2b20218538