Add vault dynamic application build from source

[StefanJum]

Add the vault applications as a dynamic build, from the application source files.
Test it using app-elfloader.
If any problems appear, open issues on the Unikraft core repository.

The typical process of adding apps to the dynamic-apps repository, built from the source files, is:

• Create the app directory that will store: the executable, depending shared libraries, configuration files, data files, etc. Name it app-name-source (e.g. app-redis-source).
• Download the source code for the application (use apt source or find the source code somwhere else, like GitHub)
• Build the application following the instructions provided.
• Update or create any configuration files, if required.
• Run the executable locally, to test it.
• Run the extract.sh script to pack the application.
• Build a bash script that does all the steps you just did (downloads the sources, builds the application, creates the config files, calls the extract.sh script).
  You can take a peek at the static-pie scripts (app-nginx for example).
• Now profit. Use app-elfloader.

Note that vault seems to come as a static-pie ELF when installing it on a Linux machine, so extra steps might be required in the building step do compile it as a dynamically linked executable (if possible).

Hackathon points: 40

[b1shtream]

@StefanJum As discussed before, Vault is not a dynamic app. It is a static binary so we can add it to the static pie application repository.

[StefanJum]

@chococandy63 you can do that, yes.
This issue though is for building Vault from source, which means you can interfere in the build process and build Vault as a dynamic executable.

Nevertheless, do add the static application in the static-pie-apps repository.