Refactor LP and implant registration logic

[Und3rf10w]

A bit of a refactor that enables us to support multiple implant and LP communication channels.

Tasks

Required

• [x] Refactor implant code to support a new transport.RegisteredServer struct.
• [x] Refactor LP code to support a new transport.RegisteredClient struct - Fixed with 86cc632
• Wrap implant's interaction and initial registration logic in a goroutine
• Wrap LP's implant registration logic in a goroutine
• [x] Fix routine_test.go to adapt to new logic changes - Fixed with 2b2be80

Desired

• [x] Refactor implant/transport.go to be able to be used by both LP and implant - Fixed with 33cd670
• Create logic in the implant to support registration of a new client
• Create logic in the LP to support registration of a new (not initial) client

[Und3rf10w]

As of 4e7fb29, routine_test.go is broken, and needs to be fixed. Adding as a task.

[Und3rf10w]

Fixed routine_test.go being broken with https://github.com/shlyuz/implant_go/commit/2b2be80c56747e79f0b2d17974338e21b2ee94ea

[Und3rf10w]

Refactored LP in 86cc632. Next step is to test if we can combine the transport and/or component packages to only maintain one version of each package

[Und3rf10w]

Okay combining the LP and implant component and config and transport modules are absolutely possible, but would require another major refactor that would involve heavy usage of build tags to not leak functionality across components. Will mull on this some...

dd90b2a helps prepare for this by making these packages identical and more generic in functionality. Confirmed that commit didn't change functionality.

[Und3rf10w]

33cd670 involved a major refactor. Now both the implant and LP component share only one codebase, making everything much easier to maintain, AND paving the way for building out the teamserver

[Und3rf10w]

I think this is probably safe to merge going forward and move the remaining tasks into new issues