Force globs to respect Git wildcard characters and eslint-config-next update

Force globs to respect Git wildcard characters, contains a potential breaking change, #256 :

Fixing this bug might mean other developers who are using git clients that set --literal-pathspecs will start getting githook errors where previously they were getting false negatives. Obviously, this is the correct behaviour but it might be disruptive. The GLOB function is only called from linter code so shouldn't have any other effects beyond githook failures.

Dependency update for @financial-times/eslint-config-next to v3 #241