Deploy to tenderly

[anxolin]

The main motivation of this PR is to deploy to our tenderly account the WatchTower.

However, during the deployment, I had to do some minor changes due to some issues I observed. Sorry for a MISC PR, but just to make it easier I documented in the description the changes and also did some code annotations giving more context (see review mode).

How to deploy this?

Since I didn't know much about this service, I created some documentation that I hope is handy for ONCALL and mantainers of this project.

It shows how to deploy, gives context of what it does. It Explains and gives pointers for all the related concepts you need to know to understand this project, so anyone can get up to speed.

Additionally this document will point out about the evolution (replacement by a distributed version)

https://www.notion.so/cownation/WatchTower-legacy-Tenderly-Composable-CoW-Indexer-8e62049feb6e440d9b097f83e054ac75?pvs=4

Local test for Tenderly Web3 Actions

To debug some issues I had to run Tenderly Actions locally to shorten the dev cycle.

• I realized there was no instructions in the README, so I added a section
• The environment vars were not being loaded from .env file, so I added dotenv lib. I think it was working for the CLI but notfor the github actions.

Allow basic Auth in the EthersJS provider

Some RPC nodes require basic auth, so i had to add it.

Allow basic Auth in the EthersJS provider

Now we support to add optionally a user and password for each

NODE_USER_100=your-user
NODE_PASSWORD_100=your-password

Reduce logs

I removed a bunch of logs, so we would write in the log only when there's relevant changes.
For example, we don't write any more "processing block XXX", but we log if we detect a new order, post to the API, etc.

Actually the logs were breaking the indexing (circular JSON dependency), see:

Also, it was making Tenderly to remove all logs and show you nothing:

Improve log messages

The issue above was a bit hard to debug cause i was not sure which log was causing this. This PR in general adds some more context on where things fail, and give you some nice outputs of requests, API responses, etc:

Not included

I still want to reiterate in other PRs to:

• Receive a notification when there's an error
• Make the execution fail if there was any errors (currently shows you all GREEN even when there was issues)
• Handle the duplicate order exception (so its not an error, and we just log that someone else posted the order)
• [Good to have] Maybe Handle the Settlement Allowance check, because right now we are posting orders that don't have the balance and allowance, so we rely on the backend to tell us. This will save them some resources....

[socket-security]

New dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
dotenv	16.3.1	environment	+0	71.6 kB	motdotla

[mfw78]

Looks great. I'll submit a PR on the env vars to isolate those that are for the forge scripts.

[mfw78]

Looks great, just the minor typo nit.