Stop removing AR from macOS env

[keith]

With bazelbuild/apple_support#601 we make our
libtool wrapper normalize ar arguments so we can handle this case and
still produce hermetic archives (which Apple's ar does not)

[keith]

im submitting this as documentation but im not sure it's really mergable since different toolchains could have different capabilities here

[UebelAndre]

You could introduce an incompatible flag for this to nudge folks over to upgrading their toolchains

[keith]

but they could also use a non-apple_support toolchain which wouldn't help this, like using @llvm / toolchains_llvm / the raw rules_cc toolchain

[UebelAndre]

but they could also use a non-apple_support toolchain which wouldn't help this, like using @llvm / toolchains_llvm / the raw rules_cc toolchain

Couldn't they constrain their toolchains on that? But that direction aside, how can I help move this forward?

[keith]

the more i think about it i think the only option is to remove libtool from the name of our wrapper since multiple places use libtool to differentiate this, and the executable could still be a libtool where this logic is needed