Explore alternatives to fetching a large set of dependencies during Pacstall's installation

[vigress8]

Is your feature related to a problem? Please describe.

Pacstall currently installs a bunch of packages that're commonly used when dealing with pacscripts, but this isn't optimal. For example, a user may never need build-essential if they never compile packages, yet they're forced to download hundreds of megabytes for no reason. This may also be an issue for servers and other devices with limited storage.

A clear and concise description of what you want to happen.

Figure out an alternative way. Only install these dependencies the first time they're needed - for example, install git the first time a -git pacscript is installed.
We already do something similar with extraction dependencies, automatically adding them to makedepends if the pacscript's source files require them.

[oklopfer]

imo this should just be delegated to makedepends externally, since scripts already have to do that for both make (the utility) and ninja-build, for example.

Just have to figure out every script that requires build-essential. Which we can really only find from reading the packaging.