move the tool/bindings_generator dart+node script into the top-level bindings_generator/ directory

[devoncarew]

• move the tool/bindings_generator dart+node script into the top-level bindings_generator/ directory
• update the docs on regenerating the bindings

---

• I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Contribution guidelines:

• See our contributor guide for general expectations for PRs.
• Larger or significant changes should be discussed in an issue before creating a PR.
• Contributions to our repos should follow the Dart style guide and use dart format.
• Most changes should add an entry to the changelog and may need to rev the pubspec package version.
• Changes to packages require corresponding tests.

Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.

[kevmoo]

...uh...I guess?

[devoncarew]

Well, this refactor isn't critical, but I think it does help to separate out the outer tool (tool/update_bindings.dart) - that you run from the cli - from the dart code that's compiled to JS and run as a node app (invoked from that initial tool). It helps clarify which dart files are compiled to JS and which aren't.

I have no issues closing the PR if you don't think its worth it; cc @kevmoo @srujzs.

[srujzs]

I don't mind, it's nice to only keep update_bindings.dart in tools so you know what file to run easily.

[srujzs]

Is the formatting done elsewhere?

[devoncarew]

we're just emitting code now that's already formatted :)