bazel: expose fix_lint and lint_test targets with public visibility

[oharboe]

Summary

Exposes fix_lint and lint_test targets in BUILD.bazel with visibility = ["//visibility:public"].

Downstream Usage

This allows downstream Bazel workspaces (such as OpenROAD-flow-scripts) to run OpenROAD's version-pinned linter toolchain (tclint, tclfmt, buildifier) directly from their workspace root without requiring local patches or aliases:

# From OpenROAD-flow-scripts repo root:
bazelisk run //tools/OpenROAD:fix_lint

Because Bazel automatically sets BUILD_WORKSPACE_DIRECTORY to whichever workspace invoked bazel run, file discovery in fix_lint.sh automatically targets ORFS files when run in ORFS.

[gemini-code-assist]

Code Review

This pull request updates the BUILD.bazel file to expose the test_suite and sh_binary targets with public visibility. The reviewer correctly pointed out that exposing the test_suite target without also exposing its constituent test targets will result in Bazel visibility errors for downstream consumers.

[oharboe]

Added visibility = ["//visibility:public"] to all constituent test targets (lint_tcl_test, fmt_tcl_test, tidy_tcl, lint_bzl_test, fmt_bzl_test, tidy_bzl) in BUILD.bazel so test_suite(name = "lint_test") resolves cleanly for downstream workspaces.

[maliberty]

Why make the tests public?

[oharboe]

Why make the tests public?

Then I can test if ORFS is formatted correctly.

[oharboe]

I don't want to duplicate the policies of OpenROAD w.r.t. coding of scripts and the infrastructure for linting and checking, I want OpenROAD to set them and ORFS to follow them.