Use persistent storage for containerbase binaries

[Gabriel-Ladzaretti]

Currently the containerbase tmp dir is /tmp/containerbase.

base/src/usr/local/containerbase/utils/constants.sh

Line 33 in bbd5b88

export CONTAINERBASE_TMP_DIR=/tmp/containerbase

This affects execution duration for micro vms that use a rootfs based on containerbase and run Renovate, as this directory is deleted at boot time.
As per the Linux Foundation: Filesystem Hierarchy Standard:

Although data stored in /tmp may be deleted in a site-specific manner, it is recommended that files and directories located in /tmp be deleted whenever the system is booted.¹

A suggested alternative location could be /var/tmp as it is preserved between boots.

The /var/tmp directory is made available for programs that require temporary files or directories that are preserved between system reboots. Therefore, data stored in /var/tmp is more persistent than data in /tmp.²

This change alone will improve boot timesruntime duration by half a second per Renovate job. given the daily throughput, this improvement adds up significantly.

Footnotes

1. https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch03s18.html ↩

2. https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch05s15.html ↩

[nabeelsaabna]

Since this is a side effect of read-only filesystem changes and the fact we run in microVMs I suggest a simple solution in which we populate both /tmp and /var/tmp with same tools content and we can set CONTAINERBASE_TMP_DIR=/var/tmp/containerbase in the hosted-app

[viceice]

we can't simply populate both paths.
some files and folders are symlinked to that tmp path from home.