[eTS] Fix function call ambiguities involving class & interface type params · Pull Request !1308 · OpenHarmony/arkcompiler_ets_frontend

#### Issue: 
#I8IOL1

#### Reason: 
there are some ambiguities when calling a function with class type parameters and interface type parameters. An example was given in the related issue.

#### Description:
`ChooseMostSpecificSignature()` has been updated: now it first looks for most specific param signature among class type params, and later among interfaces.

Unnecessary `arguments` parameter has been removed from `ChooseMostSpecificSignature()` method (as it used to be before a recent change), so now the process of choosing most specific arguments are now independent from arguments (as it used to be).

What is considered ambiguous has been decided by the recent language specification. Where there was no information, I followed the Java language behaviour in such cases.

#### Test scenarios (new, modified, affected functions):
I also added some tests that cover the problem more widely than the previous tests have. New test files and their expected behaviour can be found in the related files of this PR.

It resolves internal issue #13529.

PR to igelhaus: https://gitee.com/igelhaus/arkcompiler_ets_frontend/pulls/16

类型	指派人员	状态
审查	@egavrin 由 CODEOWNERS 文件第 15 行指派为审查者	进行中 (0/1人)
审查	godmiaozi zhuoli72 徐城	进行中 (0/1人)
测试	openharmony_ci	进行中 (0/1人)

OpenHarmony/arkcompiler_ets_frontend .gitee-modal { width: 500px !important; }

搜索帮助

OpenHarmony/arkcompiler_ets_frontend