Auto-register Plan Torchscript translator

[vvmnnnkv]

Description

In #3360 torchscript translator is auto-registered on Plan inside syft.execution.translation.torchscript.
This was relying on the fact that PlanTranslatorTorchscript is imported somewhere in __init__.py files when Syft is imported.
At some point PlanTranslatorTorchscript import was removed.
This change registers PlanTranslatorTorchscript inside syft.execution.plan.

Additionally, it fixes FL Training Plan experimental notebooks to use sy.make_hook instead of sy.hook.

Type of change

Please mark options that are relevant.

• Added/Modified tutorials
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• I have added tests for my changes
• I did follow the contribution guidelines
• I have commented my code following Google style.

[review-notebook-app]

Check out this pull request on 

You'll be able to see Jupyter notebook diff and discuss changes. Powered by ReviewNB.

[codecov]

Codecov Report

Merging #3405 into master will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #3405   +/-   ##
=======================================
  Coverage   94.70%   94.70%           
=======================================
  Files         152      152           
  Lines       16061    16061           
=======================================
  Hits        15211    15211           
  Misses        850      850           

Impacted Files	Coverage Δ
syft/execution/translation/torchscript.py	100.00% <ø> (ø)
syft/execution/plan.py	93.60% <100.00%> (+0.05%)	⬆️

[Jasopaum]

Looks good to me!
Just a small question (not sure if it's the best place to ask) but what's the new status with hooks? Does make_hook(globals) looks at all the frameworks it can hook and TorchHook hooks only Torch?

[vvmnnnkv]

Just a small question (not sure if it's the best place to ask) but what's the new status with hooks? Does make_hook(globals) looks at all the frameworks it can hook and TorchHook hooks only Torch?

Frankly, no idea :-)
sy.hook() (which was a shortcut for setting up TorchHook and creating sandbox) was renamed to sy.make_hook(), that's all I know.