Redesign Win32 build transition rules

[yukawa]

Description

This reworks my previous commits, which aimed to make it configurable on which executable should be built with what build configurations (e.g. CRT link type, target CPU architecture).

One thing we need to further consider is the debug symbol name embedded in each artifact executable as noted in 0377ddd.

To generate debug symbols one can use generate_pdb_file feature. The issue is that the pdb filename is not configurable in rules_cc. For instance, if the target name is mozc_tip32, then rules_cc assumes that the output pdb file is always mozc_tip32.pdb. To make it mozc_tip32.dll.pdb, the target name must be mozc_tip32.dll.dll. This is why I had do rework Win32 build transition rules.

Implementation note:

• The reason why mozc_win32_cc_prod_binary needs to be introduced is because the final executable name needs to be available as an input of mozc_cc_binary.
• mozc_cc_win32_library also needs to be reworked so that generate_pdb_file feature will not be applied to it.

There must be no observable change in GYP build and non-Windows bazel builds.

Closes #1108.

Issue IDs

• The symbol file name embedded in mozc_tip32.dll built with Bazel is mozc_tip.pdb rather than mozc_tip32.dll.pdb #1108

Steps to test new behaviors (if any)

• OS: Windows 11 23H2
• Steps:
  1. bazel --bazelrc=windows.bazelrc build --config oss_windows --config release_build //win32/tip:mozc_tip32
  2. cp bazel-bin\win32\tip\mozc_tip32.dll .
  3. dumpbin /headers mozc_tip32.dll | findstr cv
  4. Confirm mozc_tip32.dll.pdb is in the output.

[yukawa]

Addressed all the comments then rebased onto HEAD.