Eslint Rule unified-signatures should not flag overload functions needed for JSdoc tags

[MichaelSwigerAtBentley]

Issue: Currently, if we overload a function to deprecate an older version with different parameters, or add a new overload with new parameters, unified-signatures will flag these overloads if they can be merged into one (which is often the case). However, we cannot do this as the different signatures will have different jsdocs.

Fix: There is an eslint option for unified-signatures that will ignore overloads with different jsdocs.

We should apply this option, and remove the lint exceptions.

[hl662]

Would this change be done in iTwin/eslint-plugin, so that other pkgs can take advantage?

[MichaelSwigerAtBentley]

It depends if other consumers of the plugin use JSdocs in the same way that we do.

I was also considering removing the rule. It seems very niche, especially when most overloads we create are for compatibility reasons, and would almost certainly ignore this lint rule. What cases would the clean up our code?