[syscalls] Change vmar_... calls

- Create zx_vm_option_t type
- Change ZX_VM_FLAG_... to ZX_VM_... and make them new type.
- Change int32_t flags parameters to zx_vm_option_t options
- Make the options parameter be second.

- Modify vmar_..._old functions to keep other repos working.
Once they've all been updated these functions will go away.

ZX-2264
Test:CQ

Change-Id: I1faf4cc4e1e4dabf3d8ef680e398d83a545b0f09

[ulib][musl][asan] Emit a message for ASan vs non-ASan mismatch

All ASan-using modules depend on the ASan runtime library, which
will call __sanitizer_shadow_bounds in its initialization. When
this call is made in the non-ASan libc, there is nothing to do but
crash, which it already does. Make it log a message explaining why.

ZX-2090 #done

Change-Id: If33649429464f834625e1c5e55509bc7b36ad2af

[zx] Magenta -> Zircon

The Great Renaming is here!

Change-Id: I3229bdeb2a3d0e40fb4db6fec8ca7d971fbffb94

[ulib][musl][asan] Export __sanitizer_shadow_bounds function

This is an API the sanitizer runtime will use to get the details
of the shadow memory setup that the dynamic linker did in startup.

Change-Id: Ied30a23e702a15a5af1364145a04a4f753e3a1ae

[musl][asan][vmo] Name the shadow Vmo

Change-Id: I86cd19e93dbf31a9d288e6df41db64534e5f908b

[musl] Use new magenta errors

Change-Id: I72d62767392cb2ce84e1ed1b35a338ab3d716e4a

[ulib][musl][ldso][asan] Set up shadow memory as early as possible

In the ASan build, the dynamic linker is responsible for setting
up the shadow memory early in startup so that most of the libc
and dynamic linker code itself can be sanitized.

Change-Id: I4f4b5f1951f247deefa132ed211ad577c31f6e01