Sometimes the findFunctionName function would falsely identify a snippet somewhere around an if/while/catch construct (basically anything that had a block with it)

Description

The regex that matched with the snippet basically attempted to match anything on the form <function name><whitespace>(<parameter list>)<whitespace>{, so things like the following would match:

• foo(); } else if (b) { (); } else if (b, in this case, would be the parameter list)
• functionCall()\nif (condition) { (in this case, functionCall()\nif would be the function name)

To work around that, I changed the regex to not matching opening parenthesis, and the regex to not match any closing parenthesis.

Motivation and Context

Fixes #54

How Has This Been Tested?

I've added an unit test, and I've tested this change with some private code that also happened to trigger this bug

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• npm run lint passes without errors
• npm run test passes without errors
• I have read the contribution guidelines
• I have updated the documentation accordingly
• I have added tests to cover my changes