Hide `Adversary` instead of `Adversary.Perturber`

[mzweilin]

What does this PR do?

Hide the Adversary modules instead of Adversary.Perturber, so that we can make use of all Trainer features in Adversary.

We may configure not to hide Adversary for computing universal perturbations.

Depends on #144

Type of change

Please check all relevant options.

• [ ] Improvement (non-breaking)
• [ ] Bug fix (non-breaking)
• [x] New feature (non-breaking)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

Testing

Please describe the tests that you ran to verify your changes. Consider listing any relevant details of your test configuration.

• [x] pytest
• [x] python -m mart experiment=CIFAR10_CNN_Adv trainer=gpu trainer.precision=16 reports 70.23%

Before submitting

• [x] The title is self-explanatory and the description concisely explains the PR
• [x] My PR does only one thing, instead of bundling different changes together
• [x] I list all the breaking changes introduced by this pull request
• [x] I have commented my code
• [ ] I have added tests that prove my fix is effective or that my feature works
• [x] New and existing unit tests pass locally with my changes
• [x] I have run pre-commit hooks with pre-commit run -a command without errors

Did you have fun?

Make sure you had fun coding 🙃

[mzweilin]

Now I can see gradient logs on Tensorboard.

CUDA_VISIBLE_DEVICES=0 \
python -m mart \
experiment=CIFAR10_CNN_Adv \
fit=false \
trainer=gpu \
+trainer.limit_test_batches=1 \
+callbacks@model.modules.input_adv_test.callbacks=gradient_monitor \
+model.modules.input_adv_test.callbacks.gradient_monitor.frequency=1 \
+logger@model.modules.input_adv_test.logger=[tensorboard]

[dxoigmn]

I also doubt there is a logger associated with the adversary's trainer.

[mzweilin]

Close in favor of #160