This is required by Zig 0.12. Additionally Zig 0.12 will require a -M
flag for the main module.

Zig SDK 0.12 places stricter meaning on the order of command-line flags:
The first module to be declared is considered the main module.
Module specific options, such as configuration or target settings have
to be listed before the module that they affect.

This ordering is requried for Zig 0.12

This is requried to avoid errors of the form
```
INFO: From Building zig-docs/main.zig as Zig shared library bazel-out/k8-fastbuild/bin/zig-docs/libshared-library.so:
invalid filename
!2 = distinct !DICompileUnit(language: DW_LANG_C99, file: !3, producer: "zig 0.12.0", isOptimized: false, runtimeVersion: 0, emissionKind: FullDebug, enums: !4, globals: !229, splitDebugInlining: false)
!3 = !DIFile(filename: "", directory: "/home/aj/.cache/bazel/_bazel_aj/0deefcb713c28fbc7261691ef6069b08/sandbox/linux-sandbox/200/execroot/_main/zig-docs")
warning: ignoring invalid debug info in BitcodeBuffer
```

Configuration that is meant to be global, not just per module, needs to
be set at the end of the command line.