chore(linter): rename useExplicitFunctionReturnType to `useExplicit…

[kaykdm]

…Type`

Summary

related: #2017
rename useExplicitFunctionReturnType to useExplicitType
Before implementing the typescript-eslint/explicit-module-boundary-types rule, I renamed it for better accuracy, as discussed in the issue here .

Test Plan

[codspeed-hq]

CodSpeed Performance Report

Merging #4261 will degrade performances by 8.24%

_{Comparing kaykdm:rename-use-explict-function-return-type (cd632ba) with main (773f5b0)}

Summary

❌ 1 regressions
✅ 104 untouched benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

	Benchmark	main	kaykdm:rename-use-explict-function-return-type	Change
❌	big5-added_15586211152145260264.json[uncached]	547.4 µs	596.5 µs	-8.24%

[Conaclos]

@kaykdm The rule you implemented is not meant to cover both all cases of #2017? Why did you rename the rule then?

[kaykdm]

@Conaclos
Sorry for the late response.

• I noticed the issue title after implementing the typescript-eslint/explicit-function-return-type rule and assumed that the rule name was already decided.
• I'm planning to implement the typescript-eslint/explicit-module-boundary-types rule, so I thought it would make sense to rename the rule before proceeding with its implementation.

I don't mind reverting the rename PR if you'd prefer me to include the rename chore in the first PR with the new rule.

[Conaclos]

@kaykdm I am unsure to understand what you mean. Do you want to extend the current rule to cover #2017?

[kaykdm]

Do you want to extend the current rule to cover #2017?

@Conaclos
Yes, that was my plan, and I thought that was your plan too. If you think that we should separate the rule, that would be fine for me as well.

[Conaclos]

Thanks for the response, I will assign the task to you.