Improve the mise script

[syntrust]

Add semgrep tests for code static analysis. These tests were missing in local tests compared to CircleCI's main workflow.

Additionally, put the lint check early before solidity building. This step helps identify common format errors and can be completed quickly.

Other changes:

• environment check like RPC and kurtosis
• remove duplicated e2e tests; already included in go tests
• time metering

[blockchaindevsh]

It's helpful to add an estimation about the time to finish running it locally each time more tasks are added to it.

[syntrust]

It's helpful to add an estimation about the time to finish running it locally when more tasks are added to it.

Print time duration in the end.

[qzhodl]

It's helpful to add an estimation about the time to finish running it locally when more tasks are added to it.

Print time duration in the end.

I guess what @zhiqiangxu meant is to include a comment specifying the approximate time each added task will take to complete on a local machine?

[blockchaindevsh]

Print time duration in the end.

I mean adding a description in the PR about the incremented time and total time to run the task on local machine, we'll have to keep an eye on it to avoid it suddenly takes too much time.

[syntrust]

It's helpful to add an estimation about the time to finish running it locally when more tasks are added to it.

Print time duration in the end.

Print time duration in the end.

I mean adding a description in the PR about the incremented time and total time to run the task on local machine, we'll have to keep an eye on it to avoid it suddenly takes too much time.

It makes more sense to check the real execution time locally in person due to different hardware conditions.
It is recommended to use the script in person, and printing time in the script helps to get a feel of the duration for each step after you run it a few times.

[blockchaindevsh]

It's helpful to add an estimation about the time to finish running it locally when more tasks are added to it.

Print time duration in the end.

Print time duration in the end.

I mean adding a description in the PR about the incremented time and total time to run the task on local machine, we'll have to keep an eye on it to avoid it suddenly takes too much time.

It makes more sense to check the real execution time locally in person due to different hardware conditions. It is recommended to use the script in person, and printing time in the script helps to get a feel of the duration for each step after you run it a few times.

It doesn't need to be accurate, just a baseline we have in mind. If the reviewee doesn't provide such numbers, all other reviewers will need to do it, which means duplicated work is done multiple times.

[syntrust]

It's helpful to add an estimation about the time to finish running it locally when more tasks are added to it.

Print time duration in the end.

Print time duration in the end.

I mean adding a description in the PR about the incremented time and total time to run the task on local machine, we'll have to keep an eye on it to avoid it suddenly takes too much time.

It makes more sense to check the real execution time locally in person due to different hardware conditions. It is recommended to use the script in person, and printing time in the script helps to get a feel of the duration for each step after you run it a few times.

It doesn't need to be accurate, just a baseline we have in mind. If the reviewee doesn't provide such numbers, all other reviewers will need to do it, which means duplicated work is done multiple times.

The following newly added checks take less than 5 seconds each:

• just semgrep
• just semgrep-test
• just lint-check

The full tests run about 18 minutes on AX101, and take approximately 11 hours on my local MacBook Pro.
Hope this helps.

[qzhodl]

LGTM

[dajuguan]

The mise script runs successfully on my machine.