Include SSL negotiation timings in timings and timingPhases objects

[jschoudt]

PR Checklist:

• [X ] I have run npm test locally and all tests are passing.
• [X ] I have added/updated tests for any new behavior.
  
• [X ] If this is a significant change, an issue has already been created where the problem / solution was discussed: [https://github.com/Include timings for SSL negotiation in timings and timingPhases #3127]
  

PR Description

This adds secureConnect to the timings object and ssl to the timingPhases object when you specify time: true in the request options.

[codenirvana]

@jschoudt Great work!
One nitpick, on secureConnect the firstByte phase will changes to:
response.timingPhases.firstByte = self.timings.response - self.timings.secureConnect

Added this to our fork last month: postmanlabs#33 😅
I don't feel this project is actively maintained, otherwise we are happy to sync all the feature/fixes we are doing in our fork.

[jschoudt]

@codenirvana Thanks for the review. And yeah, I see that the PRs are a bit backed up here. I'll fix that issue you pointed out. I did this because I want this capability upstream here: artilleryio/artillery#665 so I guess I'll be stuck forking and building a custom npm until this PR gets merged. Not complaining, I get that this is no one's day job 8)

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.