Add possibility to control the truncation in bert score

[SkafteNicki]

What does this PR do?

Fixes #2673

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--2776.org.readthedocs.build/en/2776/

[codecov]

Codecov Report

Attention: Patch coverage is 33.33333% with 2 lines in your changes missing coverage. Please review.

Project coverage is 40%. Comparing base (a15ef9a) to head (ab2f08b).
Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff            @@
##           master   #2776     +/-   ##
========================================
- Coverage      69%     40%    -30%     
========================================
  Files         334     334             
  Lines       18152   18153      +1     
========================================
- Hits        12569    7180   -5389     
- Misses       5583   10973   +5390     

[Borda]

@SkafteNicki looks good, lets just check the typing :)

[Borda]

@SkafteNicki, do you have any idea why it takes so long on PT 1.13?

[SkafteNicki]

@SkafteNicki, do you have any idea why it takes so long on PT 1.13?

Not sure. If we just look at one of the new tests in this PR on 1.X it takes 75sec and in 2.X it takes 8sec. On my local laptop it takes around 4sec so it must be the 1.X build that something is wrong with.
What I can see is that all the tests that are really slow for the 1.X build is decorated with the skip_on_connection_issues decorator so I assume that maybe we are just seeing some connection issues for that build.

[SkafteNicki]

@Borda this time all of them took approximately the same amount of time so lets assume that it was a connection issue