turned setup into multi-files. Initial arm support

[Donovan-Medina]

Overview

• Setup was starting to become unwieldy the larger it grows
• broke it out into several files that setup.sh calls out
• VATER is agnostic to its hostname

Initial arm64 support

• setup will ensure dependencies will be installed for arm64 or x86_64 systems
• there is an issue with subproccess tasks for python, it likes to use uname -m which is different from dpkg --print-architecture ; meaning the subprocess when installing dependencies looks for aarch64 instead of arm64. Most packages call it arm64 instead of aarch64

[Donovan-Medina]

This was prompted by a change I saw. I noticed rous is now under dev4vater/. Anticipating future changes, we now prompt the user if the repos are correct before pulling

[Donovan-Medina]

Tested on vpshere, x86_64 --> works as intended. With the main focus being x86_64, additional development for arm64 is TBD.

Arm64 fails at vater restart, specifically with semaphore.py build, subprocess(cmd=['task', 'deps']) where it calls for a go dependency with uname -m instead of dpkg --print-architecture.

[marissaeinhorn]

Tested and working