[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

[docs][syscalls] Add TODOs about documenting system call rights

ZX-2399 #comment

Test: no functional change
Change-Id: I1f285c677e2444fcf1d720d7ecbd9f490c303962

[docs] Be explicit about guarantees on vmar_map/allocate outputs

Test: Every changed line of code has been re-executed.

Change-Id: Id2eff4bd1767c6ffbfd72a906bb37ea4b8753a52

[zircon] non-resizable VMOS

This CL introduces the first option for VMO creation
ZX_VMO_NOT_RESIZABLE that 'locks' the size of a root (non-clone) VMO

Also enables the same for COW clones via ZX_VMO_CLONE_NON_RESIZEABLE

This is meant to answer safety hazards of having a client pass
VMOs to servers which the client can resize while the server is
copying data into via a memory map.

Today this is done via ZX_INFO_HANDLE_COUNT but that turns out
is racy.

This CL also cleans up vmo-tests so they using proble_for_read
and probe_for_write instead of using unrelated syscalls to test
memory mappings.

TEST=added unittests in vmo_tests

ZX-2279 #comment progress

Change-Id: If69ce772dcccd92db83f5bda313ae2343ebb448e

[docs][syscalls] Clarify ZX_ERR_NO_MEMORY as eventually going away

Not touched:
vmo_op_range.md
vmo_set_size.md
vmo_write.md
The current text is ok for these.

ZX-2303 #comment patch

Tested: Just doc changes, read before/after.

Change-Id: I2c6e1039e2b205e9cc377b9888755fa7ac676c78

[docs] Remove VMAR note about size_t vs uint64_t

Test: n/a
Change-Id: I6b21277b8170c33b6b0d15b43d4bb5063d5406e9

[syscalls] Update parameter types and names

This CL updates the parameter types and names for a number of syscalls
to match the Zircon System API rubric. There's more work to do to make
all the syscalls conform to the rubric, but this change is a start.

Change-Id: I218ac5e7e0cbd80a8c69fef7891ad40b78b6b407

[syscalls][vmar] Prohibit using SPECIFIC_OVERWRITE with MAP_RANGE

This combination is currently unused in the codebase, and would require
complicated logic to properly rollback the address space changes if the
MAP_RANGE part of the operation fails.

Change-Id: I0058b96b3b6af24995e001b6fef8cde35d5f7e20

[docs][vmar] Be more clear about SPECIFIC_OVERWRITE behavior

Change-Id: I3e934c962b8526051cafbc4b4938041281ea9fdd

[zx] Magenta -> Zircon

The Great Renaming is here!

Change-Id: I3229bdeb2a3d0e40fb4db6fec8ca7d971fbffb94

[docs][vmar] Be more clear about what *vmar_offset* does

The docs before did not explicitly specify the behavior in the case that
neither of the SPECIFIC flags were given.

Change-Id: I61c3ec6e23bdaa8cd1f9dd9865acb0b77f21a1ab

[docs][errors] Rename all the errors in docs/ to MX_OK and MX_ERR_*

Change-Id: I62451456a83145760c6454a619d4c699ce8e9017

[vmar] Add MX_VM_FLAG_MAP_RANGE

Add a new flag MX_VM_FLAG_MAP_RANGE to have a VmMapping's range mapped
when a VMAR mapping is made.

Change-Id: I58cf558773637f1fb207cf7812d742612d50e139

[docs][syscalls] Fix all the manpages

Change-Id: Ie9ba25060f3331de8d9c178caf6332fb48fc80f5

[docs] Fix ERR names in vmar syscall descriptions.

Change-Id: I34a2270d46fbae29a4618efbfc8cb298bd371e03

[vmar][map] Require that vmo_offset + size not overflow

Change-Id: I134b81e09a80be99ce3c92667273e11b0101fbb8

[vmar] Reject map attempts with unaligned vmo_offsets

Change-Id: I9846be9d8a1062bf92706f9f77011beaa481cdc4

[vmar] Accept unaligned lengths in unmap/protect

This makes the interface a little more ergonomic to use
alongside mx_vmar_map. If a non-page-aligned len is
passed in, it is rounded up to the next page.

Change-Id: I06ff5d5f19f680d98d8430e1be6ba19caadc4cc7

[docs] Correct mx_vmar_map signature

Change-Id: I5d8d584eceb5133af377fc3259bca1e13310b438

[vm] Implement new VM Address Region syscall interface

For compatibility, allow passing a process handle instead of a VMAR
to the vmar_map/unmap/protect calls and add usermode shims that
translate the old syscalls into the new ones.

Change-Id: I9ba29921d45f47d0d068e46e113dac1d139fce52