[bug] Elapsed time include the time that users are choosing some options before hayabusa load evtx and detect alert.

[hach1yon]

Describe the bug
As you know, hayabusa show Elasped time like following.

Elapsed time: 00:01:00.210

Please report any issues with Hayabusa rules to: https://github.com/Yamato-Security/hayabusa-rules/issues
Please report any false positives with Sigma rules to: https://github.com/SigmaHQ/sigma/issues
Please submit new Sigma rules with pull requests to: https://github.com/SigmaHQ/sigma/pulls 

It seems that Elapsed time include the time that users are choosing some options before hayabusa load evtx and detect alert.
I mean options are followings.

❯ 1. Core (1617 rules) ( status: test, stable | level: high, critical )
  2. Core+ (2723 rules) ( status: test, stable | level: medium, high, critical )
  3. Core++ (3718 rules) ( status: experimental, test, stable | level: medium, high, critical )
  4. All alert rules (4208 rules) ( status: * | level: low+ )
  5. All event and alert rules (4314 rules) ( status: * | level: informational+ )
✔ Include Emerging Threats rules? (218 rules) · yes
? Include sysmon rules? (799 rules) (y/n) › yes

I think we don't have to include the time that users are choosing some options into Elasped time.

Step to Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

• OS: [e.g. Windows 10 Version 20H2]
• hayabusa version [e.g. v1.0.0]

Additional context
Add any other context about the problem here.