Default ExecuTorch targets to ExecuTorch-wide Buck visibility

[swolchok]

IMO, Buck visibility is just inverse deps. We should trust that people have a good reason to add deps rather than attempt to police them and require double entry in both deps and visibility, especially since we seem to be committed to APIs by default in OSS anyway.

Specific motivation is that #8712 would otherwise have to ad-hoc slap ExecuTorch-wide visibility on a lot of targets, but I've held this view for a long time.

Differential Revision: D70647462

[swolchok]

Stack from ghstack (oldest at bottom):

• Test most of //runtime in unittest-buck #8713
• Use runtime.python_library in our BUCK/TARGETS files #8712
• -> Default ExecuTorch targets to ExecuTorch-wide Buck visibility #8969

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/8969

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit ea92179 with merge base 6346348 ():
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[mergennachin]

Can we make this consistent both internally in fbsource and shim layer?

Otherwise, a package could be potentially be private in fbsource but visible to ET in OSS, which could lead to diff train issues

[mergennachin]

Oh wait, is this file shim_et/xplat/executorch/build/runtime_wrapper.bzl actually the same file used both internally and externally?

[swolchok]

@swolchok has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[swolchok]

Oh wait, is this file shim_et/xplat/executorch/build/runtime_wrapper.bzl actually the same file used both internally and externally?

yes. (also it appears the default visibility is PUBLIC in OSS)