Add ESLint rule to avoid unintentional dependency on @wp-playgrounds/wordpress-builds

[brandonpayton]

Motivation for the change, related issues

We've encountered issues like #2026 where an undesired dependency on @wp-playground/wordpress-builds (which is an unpublished, private package) caused problems.

Implementation details

This PR adds an ESLint rule that considers dependency on @wp-playground/wordpress-builds to be an error. If a module wants a dependency on that package, it can disable the ESLint rule for the import line.

We should improve the rule message to better communicate the above.

Please feel free to take this and finish if you are interested. Otherwise, I can wrap later.

Testing Instructions (or ideally a Blueprint)

• Add an ESLint rule tester test for this and ensure it is run as part of CI
• CI

[brandonpayton]

Lint is failing in CI because the rule is working and we still need to make some exceptions.

We need to disable the rule for intended users of wordpress-builds like the remote package. Example error here:
https://github.com/WordPress/wordpress-playground/actions/runs/12146203002/job/33869569177?pr=2048#step:4:218

We also need to disable the rule for tests. Example errors here:
https://github.com/WordPress/wordpress-playground/actions/runs/12146203002/job/33869569177?pr=2048#step:4:188

[adamziel]

Agreed about the exceptions, other than that it looks good 👍

[adamziel]

Poke for after the support rotation @brandonpayton

[adamziel]

Yay, thank you!