Migrate IexecAccessors tests to ethers v6

[james-toussaint]

See job logs on Run test step ✔️ :

• https://github.com/iExecBlockchainComputing/PoCo/actions/runs/13311709870/job/37175648195

npm run test test/byContract/IexecAccessors/**
[...]
  54 passing (5s)

[gfournieriExec]

why remove that ?

[james-toussaint]

Good catch, some old testing, updated with Re-add timeref check, thanks 👍

[Le-Caignec]

Suggested change

	return ethers.TypedDataEncoder.hashDomain({
	return TypedDataEncoder.hashDomain({

other option: directly import TypedDataEncoder module

[james-toussaint]

Sure see Import from ethers (same comment everywhere)

[Le-Caignec]

An other way to do that, that we use in SDK

export const getEventFromLogs = ({ contract, eventName, logs }) => {
  const filter = contract.getEvent(eventName);
  if (!filter) {
    throw new Error(`Event filter not found for ${eventName}`);
  }

  const eventTopic = filter.fragment.topicHash;
  // Find the event in the logs based on the topic
  const eventFound = logs.find((log) => log.topics[0] === eventTopic);
  if (!eventFound) {
    throw new Error(`Event ${eventName} not found in logs`);
  }

  // Check if the event is already decoded
  if (eventFound.args) {
    return eventFound;
  }

  // If not decoded, decode the event
  try {
    return {
      ...eventFound,
      args: contract.interface.decodeEventLog(
        filter.fragment,
        eventFound.data,
        eventFound.topics
      ),
    };
  } catch (error) {
    throw new Error(`Failed to decode event ${eventName}: ${error.message}`);
  }
};

[Le-Caignec]

In fact log.topics.includes(eventId) could be replace by log.topics[0] === eventTopic. Indeed this is the first element of the topic that correspond to the event signature.
Other improvements could be considered, such as removing the need to use the address.

[james-toussaint]

FYI, took from here https://github.com/iExecBlockchainComputing/iexec-voucher-contracts-it/blob/develop/test/utils/poco/IexecWrapper.ts#L290