skip id-destructuring bugfix when binding info is not found

[JLHwung]

Q	A
Fixed Issues?	Fixes #13907
Patch: Bug Fix?	Y
Major: Breaking Change?
Minor: New Feature?
Tests Added + Pass?	Yes
Documentation PR Link
Any Dependency Changes?
License	MIT

In #13842 we detect the pattern function a([a]) {} from the scope info. This PR handles situations when

1. babel-helper-function-name injects the function id and mark them as NOT_LOCAL_BINDING, in this case the id will not be registered as constant violation
2. a plugin injects an id but does not update scope info accordingly

For the plugin to work, the assumption now is that the scope info of function parameters can be trusted: so we can avoid scanning parameters.

[babel-bot]

Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/49597/

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 9197856:

Sandbox	Source
babel-repl-custom-plugin	Configuration
babel-plugin-multi-config	Configuration

[nicolo-ribaudo]

If we are in Case 2, it means that the function didn't originally have a paramter with the same name of the new injected id?

e.g. does this work?

let x = function ([a]) {};

// plugin
Function(path) {
  path.node.id = t.identifier("a");
}

(if it doesn't it's ok - the plugin needs to be fixed)

[JLHwung]

Yeah it works if the path is then requeued (as is shown in the https://github.com/babel/babel/pull/13910/files#diff-9c3e0b47cab12356380982d8d3c8b5c3bbf3e160e18448619c2b54e9106bcb03) so that the bugfix can have a chance to be executed again.