Initial rework of decorator warnings

[rg936672]

PR Type

• Feature

Description

Decorators now check against a known "safe list" of overrides and new methods before raising a warning. This should reduce the number of spurious warnings that end users see. So far this has only been implemented for BinaryClassification above VariationalInference; expanding this to other decorators is left to future PRs.

Also improves the warning messages when they are raised, making it clearer exactly where the problem is coming from.

Progresses #123 but does not close it.

How Has This Been Tested?

Existing tests all pass. Added a temporary test to test_decorator_combinations to check that no spurious warnings are raised; this test should be incorporated into the general combinations test once implemented for all decorators.

Does this PR introduce a breaking change?

No.

Checklist before requesting a review

• I have made sure that my PR is not a duplicate.
• My code follows the style guidelines of this project.
• I have commented my code, particularly in hard-to-understand areas.
• I have performed a self-review of my code.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.
• Any dependent changes have been merged and published in downstream modules.

[pc532627]

@rg936672 Thanks for the changes, a few comments more for clarity rather than requesting code changes