crosvm: allow madvise(MADV_HUGEPAGE) in aarch64 seccomp policies

Glibc 2.43 enables Transparent Huge Pages on aarch64 and calls
madvise(MADV_HUGEPAGE) in addition to madvise(MADV_GUARD_INSTALL).

The aarch64 device seccomp policies were updated for MADV_GUARD_INSTALL
but not MADV_HUGEPAGE, so after the glibc uprev a crosvm device process
gets a SIGSYS during VM startup as soon as its allocator touches a huge
page.

This crashes crosvm while bringing up ARCVM and breaks
tast.arc.Optin.vm on asurada:
  crash_reporter: Received crash notification for crosvm[6676] sig 31,
  user 299 group 299

Add MADV_HUGEPAGE to the madvise rule in the three aarch64 policies
that define one.

BUG=b:491765858
TEST=Local asurada board builds against glibc 2.43; CQ.

Change-Id: Ide03602227b099d63d064a3d974e8550e05a25a2
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/8131376
Auto-Submit: Adrian Ratiu <adrian.ratiu@collabora.corp-partner.google.com>
Reviewed-by: George Burgess <gbiv@chromium.org>
Commit-Queue: Allen Webb <allenwebb@google.com>
Reviewed-by: Allen Webb <allenwebb@google.com>
Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org>