Bump up the pytorch lightning to master branch due to vulnurability issues

[samet-akcay]

Description

• anomalib currently uses pytorch-lightning v1.3.6, which uses yaml unsafe loader, causing vulnurabilities. According to @LeonidBeynenson, this vulnurability has been addressed in the master branch v1.6.0dev, but has not been released as a package yet. Therefore we use git+https in requirements/base.txt

Known Issues

• ScoreNormalization currently fails. Need to investigate what would be causing this issue.

Changes

• 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)
• This change requires a documentation update

Checklist:

• My code follows the pre-commit style and check guidelines of this project.
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• 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 tests pass locally with my changes

[ashwinvaidya17]

Thanks for the efforts and chasing all the issues due to the upgrade. Since this is not backward compatible, I would have proposed a major version bump up but I am concerned it might break things in OTE.

[samet-akcay]

@ashwinvaidya17, maybe we could start thinking about having a master branch.

What we could do is to merge other outstanding PRs to developmen first. We could then create a master branch. This PR could be finally merged to development. Once we ensure that OTE works with these changes, we could merge this to master as well.