[v1.10] Expose memory mapping; Make memfile dump optional

[ValentaTomas]

To gain more control over memfile handling during snapshotting, we modify the snapshot logic to optionally skip dumping the memfile.

Also, we add info about the memory regions when requesting instance info, so we can copy the memory directly.

This is fully compatible with FC v1.10.

This PR is for viewing code changes only and won't be merged.

---

Note

Adds GET /memory and /memory/mappings APIs for resident/empty page bitmaps and region mappings, and makes snapshot memory dump optional via mem_file_path.

• API:
  • Add GET /memory and GET /memory/mappings endpoints, parsing, and responses returning MemoryResponse (resident/empty bitmaps) and MemoryMappingsResponse.
  • Extend InstanceInfo with optional memory_regions; wire responses in ParsedRequest::convert_to_response.
  • Update Swagger (firecracker.yaml) with new paths and definitions.
• VMM/VM:
  • Introduce GuestMemoryRegionMapping and methods to gather mappings and memory info using mincore and zero-page detection; validate uniform page size.
  • Make snapshot memfile optional: CreateSnapshotParams.mem_file_path: Option<PathBuf> and dump memory only when provided.
• Security/Seccomp:
  • Allow mincore syscall in seccomp profiles (x86_64, aarch64).
• Tests:
  • Add unit/integration tests for new endpoints (pre-boot unsupported, post-boot success) and snapshot changes; include a non-CI memory benchmark.
• Tooling:
  • Add build/upload scripts, Makefile targets, .tool-versions; update .gitignore to include .env.

^{Written by Cursor Bugbot for commit 6c05dd5. This will update automatically on new commits. Configure here.}

[ValentaTomas]

We might also make the snapfile optional/return it as content instead.

[jakubno]

bugbot run