[IMP] l10n_tr_nilvera_einvoice: add tests

[fw-bot]

Currently we're lacking tests for the Nilvera API integration. This
commit adds a test suite that primarily focuses on testing that.

Task ID: 4655864

Forward-Port-Of: #216179

[robodoo]

[fw-bot]

@SaddemAmine @alialfie cherrypicking of pull request #216179 failed.

stdout:

Auto-merging addons/l10n_tr_nilvera_einvoice/models/account_move.py
CONFLICT (content): Merge conflict in addons/l10n_tr_nilvera_einvoice/models/account_move.py
Auto-merging addons/l10n_tr_nilvera_einvoice/tests/__init__.py
CONFLICT (add/add): Merge conflict in addons/l10n_tr_nilvera_einvoice/tests/__init__.py

Either perform the forward-port manually (and push to this branch, proceeding as usual) or close this PR (maybe?).

In the former case, you may want to edit this PR message as well.

⚠️ after resolving this conflict, you will need to merge it via @robodoo.

More info at https://github.com/odoo/odoo/wiki/Mergebot#forward-port

[SaddemAmine]

In the previous impl we disregarded the compute method verifying the partners' statuses. I think it's better to revert this to prevent regression. It's unfortunately not a "test" since we check this during the setUpClass but I think it's good enough.

[fw-bot]

@SaddemAmine @alialfie this forward port of #216179 is awaiting action (not merged or closed).

[SaddemAmine]

In this FW we adapt the changes in original PR to work with l10n_tr_nilvera_einvoice_extended since both modules utilize the same common file. We also integrate already existing tests from the previous implementation that test multicurrency scenarios and earchive exports. The aforementioned will not be backported to 17.0 following the stable policy currently only allowing critical changes to be committed in unsupported versions.

[SaddemAmine]

The test partners VAT change is needed to comply with the base_vat TR format even though, AFAIK, we noticed that Nilvera itself (which communicates straight with the Turkish government) can have VAT numbers that follow other formats.

[alialfie]

As discussed, a new PR #229724 has been created to remove the file for the skipped tests that were conflicting with this FW port. This FW port will now only be concerned with the mocking part for testing which should be in a new file specifically for mocking API calls.

@SaddemAmine Please update the PR and the commit message accordingly :D

[SaddemAmine]

To clarify how this FW is being handled: first, we decided to keep the check in _compute_nilvera_customer_status_and_alias_id within l10n_tr_nilvera_einvoice and add an additional safeguard to make sure the compute still runs when mocking Nilvera endpoints and executing the TestTRNilveraEInvoice suite.

Second, as Ali mentioned, the tests introduced here are strictly about ensuring proper interaction with Nilvera. All XML generation tests are now handled in l10n_tr_nilvera_einvoice_extended and should be merged back into l10n_tr_nilvera_einvoice as of saas~18.4.

[FlorianGilbert]

Can we r+ now? @alialfie @SaddemAmine

[SaddemAmine]

@FlorianGilbert Yup
Should be good to go

[SaddemAmine]

robodoo r+

[alialfie]

robodoo r-

@SaddemAmine You forgot to change the file name, no?

[SaddemAmine]

Yuup, completely slipped my mind
IIRC we should be good now
What do you think ? @alialfie

[alialfie]

Thanksss
robodoo r+