Auto-generate a classifier Capabilities summary #997

[BINAYKUMAR943]

Reference Issues/PRs

What does this implement/fix? Explain your changes.

This PR automatically generates a summary of the capabilities of the different classifiers. Some classifiers such as ProximityStump, ProximityTree etc. doesn't have any capabilities defined in their class. The code is currently putting N/A for them, but it will be included in the table once it gets added.

Does your contribution introduce a new dependency? If yes, which one?

No

What should a reviewer concentrate their feedback on?

Please review the part which is automatically generating the capabilities of the classifier. If it seems fine then we can generate a list like this for all the estimators. Code is just putting N/A in the table to the capabilities for the classifiers that do not have any capabilities defined.

Any other comments?

Please review and approve it. @TonyBagnall @ABostrom

PR checklist

For all contributions

• Optionally, I've updated sktime's CODEOWNERS to receive notifications about future changes to these files.
• I've added unit tests and made sure they pass locally.

For new estimators

• I've added the estimator to the online documentation.
• I've updated the existing example notebooks or provided a new one to showcase how my estimator works.

[TonyBagnall]

hi, there are I'm afraid strict formatting rules for submissions which you code failed the test for. Read here https://github.com/alan-turing-institute/sktime/blob/main/CONTRIBUTING.md

[TonyBagnall]

click on "details" next to the code quality and it will tell you why it failed. If you are on a command line you can use the pre-commit tool to check if it passes beforehand

[TonyBagnall]

if you are on a command line you can check beforehand with pre-commit, although I cannot get this working with github desktop

[BINAYKUMAR943]

if you are on a command line you can check beforehand with pre-commit, although I cannot get this working with github desktop

I have made some changes to the code and followed the suggested steps.

[BINAYKUMAR943]

click on "details" next to the code quality and it will tell you why it failed. If you are on a command line you can use the pre-commit tool to check if it passes beforehand
Thank you a ton for the suggestion. I have made some changes and checked using the pre-commit tool in my locals. It is passing now.

[TonyBagnall]

I'll put this in as its in contrib, we can refactor it for tags later

[BINAYKUMAR943]

I'll put this in as its in contrib, we can refactor it for tags later

Sure, Thanks!