Add a wrapper so that the module can be used with the new module API

[reivilibre]

Fixes #133

Alternative to #134.

[clokep]

Seems OK. I think it would make sense to include the tests in this PR.

I guess it isn't doable to use the same class directly? Since the class itself doesn't know how it is registered?

[reivilibre]

I guess it isn't doable to use the same class directly?

I did this originally, but got told to do it this way. I think this way is cleaner even if just because the callbacks need their signatures massaging through the wrappers.

[reivilibre]

@clokep I've now bundled the changes to the tests in this PR, as suggested.

[reivilibre]

I guess it isn't doable to use the same class directly?

I did this originally, but got told to do it this way. I think this way is cleaner even if just because the callbacks need their signatures massaging through the wrappers.

(I think we will eventually want to cut out the 'old way'; at that point it would be sensible to remove the wrapper.)

[clokep]

(I think we will eventually want to cut out the 'old way'; at that point it would be sensible to remove the wrapper.)

But we would have to ask people to update their Synapse config again though, which is really not ideal. This is why I was asking!

[reivilibre]

(I think we will eventually want to cut out the 'old way'; at that point it would be sensible to remove the wrapper.)

But we would have to ask people to update their Synapse config again though, which is really not ideal. This is why I was asking!

I think we would just stick with the name with 'Module' on the end; we do that for some other modules so it wouldn't be that much out of place