fix typo in specificity_at_sensitivity

[oguz-hanoglu]

What does this PR do?

• specicity used instead of specificity -> Fixed.
• The issue was: init.py has duplicates (class based one), init.py's are not organized in the same order (functional and class based)
• The issue addressed as removing duplicates and reorganizing the list order.

Before submitting

• Was this discussed/agreed via a Github issue? (no need for typos and docs improvements)
• Did you read the contributor guideline, Pull Request section?
• Did you make sure to update the docs?
• Did you write any new necessary tests?

PR review

Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.

Did you have fun?

• Make sure you had fun coding 🙃

---

📚 Documentation preview 📚: https://torchmetrics--2199.org.readthedocs.build/en/2199/

[Borda]

it si breaking change but worse to fix it

[codecov]

Codecov Report

Merging #2199 (3fea3fa) into master (245ee24) will decrease coverage by 39%.
Report is 1 commits behind head on master.
The diff coverage is 51%.

Additional details and impacted files

@@           Coverage Diff            @@
##           master   #2199     +/-   ##
========================================
- Coverage      87%     47%    -39%     
========================================
  Files         293     293             
  Lines       16437   16469     +32     
========================================
- Hits        14275    7807   -6468     
- Misses       2162    8662   +6500     

[oguz-hanoglu]

@Borda To avoid any misunderstandings among other reviewers, could you please clarify your comment? I assume you mean: "It is not a breaking change, but it is worth fixing." Am I correct?