Add hasInstall and hasUninstall relationships

[JPEWdev]

Adds relationships that indicate the installation and uninstallation of artifacts during a lifecycle scope (e.g. build, runtime, etc.)

[kestewart]

Usecase coming from Yocto project. Root file system image contains files, and files are contained by packages came from. Can only link root file systems to packages via contains & files. Will be useful to be able to be explicitly - install and uninstalled. Illustrate not used in root file system. Runtime dependencies being uninstalled is not quite the right semantic. What's on shipping vs. being running.

Should the supply chain action be used? Installed on a platform, not artifact? Not quite, can do a cross compile. Image being manipulated outside the context. Host platform is capture in build profile.

Can install things in build time vs run time. Period type? Definition of the word install? apt install, brew, ... boot loader installing a system image.

Possibly lifecycle scope extension - manufacturing? (consider later)

Don't want to conform to supply chain profile. No conformance points though right now.

Artifact installing, indicates method likely. ie. debian package; debian pkgs, apt.

Installing is placing in position for use?