use common interface for v2.3

[shileiwill]

As title, several considerations in this PR:

1. We use the common interface 100%, and compatible Utils as much as possible, but there is an edge case for Report. So we decided to keep the Utils2_3. We keep only the Report and removed all others. This ensures we have the right naming (linkUSD v.s. linkNative), and having the Utils2_3 doesn't break any backward compatibility.
2. In typescript test, we replaced setConfig with setConfigTypeSafe, which means we lost coverage on setConfig. However, we have setConfig covered in foundry test.

[github-actions]

I see that you haven't updated any README files. Would it make sense to do so?

[FelixFan1992]

As title, several considerations in this PR:

1. We use the common interface 100%, and compatible Utils as much as possible, but there is an edge case for Report. So we decided to keep the Utils2_3. We keep only the Report and removed all others. This ensures we have the right naming (linkUSD v.s. linkNative), and having the Utils2_3 doesn't break any backward compatibility.
2. In typescript test, we replaced setConfig with setConfigTypeSafe, which means we lost coverage on setConfig. However, we have setConfig covered in foundry test.

for (2), i think it's totally fine (or EVEN BETTER!) to test set config in foundry!

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube