Fix: no-extra-strict behavior for named function expressions (fixes #1209)

I don’t know if this is the best solution to fix #1209.

The problem is that `escope` creates a separate scope for named function expressions (see: [escope#7](https://github.com/Constellation/escope/issues/7)).