Improve UnnamedParameterUse message (change CALL_EXPRESSION to actual function name)

[TWiStErRob]

I got some reports from this rule while testing detekt 2 upgrade:

....kt:49:9: CALL_EXPRESSION uses unnamed parameters. Consider using named parameters as they make usage of function more safe [UnnamedParameterUse]
....kt:54:12: CALL_EXPRESSION uses unnamed parameters. Consider using named parameters as they make usage of function more safe [UnnamedParameterUse]
....kt:59:9: CALL_EXPRESSION uses unnamed parameters. Consider using named parameters as they make usage of function more safe [UnnamedParameterUse]

to find the reported element I have to resort to lines and offsets. I'm guessing that the original intent was to put the text of the expression there instead of CALL_EXPRESSION.

While changing this behavior I also focused the report on the function name itself rather the the whole expression to prevent the usual large yellow blow in IDE (see #5316 for example).

Rule was added in #6055 cc @atulgpt (can't add you as reviewer for some reason)

[codecov]

Codecov Report

Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (1456279) 84.83% compared to head (7957c4a) 84.83%.

Files	Patch %	Lines
...rturbosch/detekt/rules/bugs/UnnamedParameterUse.kt	66.66%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #6681      +/-   ##
============================================
- Coverage     84.83%   84.83%   -0.01%     
  Complexity     4098     4098              
============================================
  Files           570      570              
  Lines         13179    13180       +1     
  Branches       2418     2419       +1     
============================================
  Hits          11181    11181              
  Misses          789      789              
- Partials       1209     1210       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[cortinico]

@BraisGabin heads up: this PR was flagged as pick request but this rule doesn't exist in 1.x so I won't be picking it