fix: Add #[track_caller] to many address, page, and frame methods

[mkroening]

This PR adds a bunch of #[track_caller] attributes to creation and arithmetic on VirtAddr, PhysAddr, Page, and Frame. This makes Rust panic messages point to the problematic user code (or higher-level code in this crate) instead of the code that is expected to panic on certain inputs.

Example:

PhysAddr::new(u64::MAX);

Before:

panicked at /Users/mkroening/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/x86_64-0.16.0-rc.0/src/addr.rs:551:23:
physical addresses must not have any bits in the range 52 to 64 set

After (my kernel):

panicked at src/arch/x86_64/mm/paging.rs:226:5:
physical addresses must not have any bits in the range 52 to 64 set

This is very useful for debugging issues such as #611 but is also useful in general for users.

There might be more places where #[track_caller] might make sense, but these should be the obvious ones.

[phil-opp]

Good idea, thank you!