backport: remove all custom class instantiation of synapse-sdk classes

[SgtPooki]

we should be using the synapse instance we have, and methods we need should be exposed, or we should do what is otherwise recommended..

There may be use-cases where we might need to instantiate a custom WarmStorageService or PDPVerifier, but i'm thinking we probably shouldn't be doing this. We need to backport our usecases to synapse-sdk and make sure methods are exposed that allow us to do what we need "in the right way"

some classes we instantiate in filecoin-pin that we probably shouldn't, because there isn't a top-level API for doing what we want:

1. new PDPVerifier
2. new PDPServer
3. WarmStorageService.create
4. new SPRegistryService

NOTE: any changes here will likely require agreed-upon plans with the synapse-sdk core devs and changes to synapse-sdk

[rvagg]

I think it's OK for you to use custom instances of them, and even be reaching into synapse-core for things where some of these bits of functionality are duplicated (being extracted and then wrapped back in synapse-sdk; we might need to address that duplication in the future). But, each time we use them for custom things we should be asking if it's for something that Synapse should be doing for you, maybe the functionality should be pushed back into Synapse.