calculate tx the lifecycle duration

[georgehao]

1. Purpose or design rationale of this PR

Calculate the tx median lifecycle duration.

Background is here: https://www.notion.so/scrollzkp/7ba4e2226275414692228f6332d85621?v=d8d35fc59bae4ad1acf48fdfc616934e&p=2a41bd0b70d54211a7b34e1ea766b14a&pm=s

2. PR title

Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:

• [ ] build: Changes that affect the build system or external dependencies (example scopes: yarn, eslint, typescript)
• [ ] ci: Changes to our CI configuration files and scripts (example scopes: vercel, github, cypress)
• [ ] docs: Documentation-only changes
• [x] feat: A new feature
• [ ] fix: A bug fix
• [ ] perf: A code change that improves performance
• [ ] refactor: A code change that doesn't fix a bug, or add a feature, or improves performance
• [ ] style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
• [ ] test: Adding missing tests or correcting existing tests

3. Deployment tag versioning

Has the version in params/version.go been updated?

• [ ] This PR doesn't involve a new deployment, git tag, docker image tag, and it doesn't affect traces
• [x] Yes

4. Breaking change label

Does this PR have the breaking-change label?

• [x] This PR is not a breaking change
• [ ] Yes

[HAOYUatHZ]

here we don;t distinguish the "end time" for

1. tx is included
2. tx is dropped

then how can it serve your need? we wouldn't know a "lifecycle duration" is for being included or being dropped

[georgehao]

here we don;t distinguish the "end time" for

1. tx is included
2. tx is dropped

then how can it serve your need? we wouldn't know a "lifecycle duration" is for being included or being dropped

tx is included we can know this, i think tx is dropped yes, can't get this. this will affect the p90 statistics, for p50 it's ok