Rename profiler directory to profilers

[Pragyanstha]

[rebase and merge]

What does this PR do?

Closes #11972.

• Consists of two commits:
  • Commit 1:
    • rename profiler/ directory to profilers/.
    • update import statements all over the repository.
  • Commit 2:
    • reroute profiler/ to profilers/ with the deprecation warning.
    • put back items that had already been deprecated in the previous PRs.

Does your PR introduce any breaking changes? If yes, please list them.

No, it just deprecates profiler/* in favour of profilers/*.

Before submitting

• Was this discussed/approved via a GitHub issue? (not for typos and docs)
• Did you read the contributor guideline, Pull Request section?
• Did you make sure your PR does only one thing, instead of bundling different changes together?
• Did you make sure to update the documentation with your changes? (if necessary)
• [n/a] Did you write any new necessary tests? (not for typos and docs)
• Did you verify new and existing tests pass locally with your changes?
• Did you list all the breaking changes introduced by this pull request?
• Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review

Anyone in the community is welcome to review the PR.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

• Is this pull request ready for review? (if not, please submit in draft mode)
• Check that all items from Before submitting are resolved
• Make sure the title is self-explanatory and the description concisely explains the PR
• Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?

maybe

[rohitgr7]

LGTM! mind add a changelog entry?

[kaushikb11]

A second PR would be created for adding back the previous API that redirects the call into the new API,
with a deprecation warning.

I think you should add it in this PR

[rohitgr7]

A second PR would be created for adding back the previous API that redirects the call into the new API,
with a deprecation warning.

I think you should add it in this PR

it will create a lot of changes in a single one since git file-renames won't be valid then.

[carmocca]

LGTM but this should go after the release to make sure we have time for the deprecation too.

[tchaton]

LGTM !

[daniellepintz]

@Pragyanstha mind rebasing this PR?

[ananthsub]

As is, this PR is a breaking change for those on master, which we should avoid.

I would strongly recommend doing both of these in the same PR to avoid any breaking change:

• Copy the existing code over to a profilers/ directory
• In the existing profiler/ directory, import the components from the new profilers/ directory and include the relevant deprecation warnings

[rohitgr7]

As is, this PR is a breaking change for those on master, which we should avoid.

I would strongly recommend doing both of these in the same PR to avoid any breaking change:

* Copy the existing code over to a profilers/ directory

* In the existing profiler/ directory, import the components from the new profilers/ directory and include the relevant deprecation warnings

wouldn't that create a huge git diff for reviewers? I think we did the same for training type plugin -> strategy. This is targeted after v1.6, so we can quickly create another one once this is merged.

[carmocca]

Included a change in the last commit that should fix the cli failures