flowey: report size of initramfs/initrd in build processes, and how large each item is.

[chris-oo]

I'd like to see how large our initrd is, i wonder if the debug binsize even stripped, is huge now.

Originally posted by @chris-oo in #2407 (comment)

[chris-oo]

I'm not sure if this is easy to do, or if we'd have to do it via a vmm_test, but some back of the envelope calculations show that running a dev build locally du reports the following for disk usage via shell:

190M    .
sh-5.1#

and df reports:

sh-5.1# df
Filesystem     1K-blocks   Used Available Use% Mounted on
rootfs            208272 194296     13976  94% /

note that memfree here shows this:

❯ uh ohcldiag-dev inspect proc/meminfo
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.22s
     Running `target/x86_64-pc-windows-msvc/debug/ohcldiag-dev.exe 'c:\users\cho\appdata\local\temp\uhdiag' inspect proc/meminfo`
{
    AnonPages: 14972,
    Committed_AS: 232504,
    KernelStack: 800,
    Mapped: 28880,
    MemFree: 240916,
    MemTotal: 492480,
    PageTables: 716,
    Percpu: 180,
    SUnreclaim: 4728,
    Shmem: 194296,
    Slab: 6800,
}

which to me, means that if the kernel's size of initramfs is MemTotal/2 = ~240 mb (but smaller due to some different kernel size calculations). Which means we were probably close to running out of space.

Note that on a release build we have 18MB of du reported usage, with memtotal being MemTotal: 56956. df doesn't seem to list anything useful, but we have a lot more free space in that case.