Transition to uber fx

[kristinapathak]

In general, we want to transition our applications over to the uber fx framework. Since tr1d1um is relatively small and straightforward, we want to start here. This is also a good opportunity to move away from the webpa-common library, which is slowly being deprecated. Below are some of the things we will need to transition:

• Use arrange to help with configuration and other uber fx wiring.
• Move to zap logging. Sallust will help with this.
• Use basculehttp Provide functions for easier setup of bascule middleware.
• Use touchstone for prometheus compatible metrics.
• Set up http servers and clients with httpaux.
• No longer import webpa-common directly into any tr1d1um package. After these other changes, the only package remaining should be device. We will need to either move the functionality to a new module (this is my preference) or put the functionality we need into tr1d1um directly.

[kristinapathak]

Talked with @schmidtw and @johnabass and we tentatively agreed on moving device ID functionality to wrp-go.

[denopink]

closed by #295