Migrate PAVICS deployment to use a pluggable architecture

[mishaschwartz]

As a first step to creating a DACCS deployment mechanism, we should update the PAVICS deployment.

This will help us understand the current PAVICS deployment and how all the various components currently interact. We need to fully understand the current architecture before we create a more general DACCS deployment process.

Relevant PRs (in birdhouse-deploy):

• Migrate existing pieces to new pluggable component architecture, part 1 clean up the unused pieces bird-house/birdhouse-deploy#214
• Migrate existing pieces to new pluggable component architecture, part 2 the simple pieces bird-house/birdhouse-deploy#213
• Migrate existing pieces to new pluggable component architecture, part 3 the rest of the birds and twitcher/magpie into one big component bird-house/birdhouse-deploy#215
• Migrate existing pieces to new pluggable component architecture, part 4, the front proxy bird-house/birdhouse-deploy#216
• Migrate existing pieces to new pluggable component architecture, part 5, decouple platform autodeploy from notebooks autodeploy bird-house/birdhouse-deploy#217
• Migrate existing pieces to new pluggable component architecture, part 6 extract generic docker-compose utitlies into a separate repo bird-house/birdhouse-deploy#219
• 💡 [Feature] Protected ports by design bird-house/birdhouse-deploy#222

[mishaschwartz]

All components are now fully pluggable.