fix: Refactor Token Processing Logic

[0xwitty]

I've refactored the fetchData function and related token processing logic to improve performance, clarity, and maintainability. Here's a summary of the changes:

1. Switched to fetch: Replaced the outdated XMLHttpRequest with fetch for cleaner syntax and better performance.
2. Lisk Token Filtering: Added logic to filter only relevant Lisk chain tokens (1135 and 4202).
3. Ethereum Token Matching: Ensured tokens are matched on Ethereum Mainnet or Sepolia using chainId and symbol.
4. Dynamic Explorer Selection: Introduced dynamic selection of explorers (etherscan or blockscout) based on the token's network.
5. Modular Structure: Improved readability and reusability by breaking the code into helper functions, such as createTableRow.
6. Modern JavaScript: Utilized modern syntax, including async/await, filter, and object destructuring, for cleaner and more maintainable code.

This resolves the issue while enhancing the overall code quality.

[Tschakki]

Hey @0xwitty ,
thanks for your effort!
Unfortunately, when I build the docs based on your branch the bridged token page shows several errors, and doesn't display the token addresses. Can you fix it?

To reproduce, run npm run build and then npm run serve