Make scan session id available for full life cycle of scan session.

[keith-turner]

Is your feature request related to a problem? Please describe.

Scans on tablet servers create scan session ids which are 64 bit secure random ids. These ids are strong selectors when grepping log files and including them in more log messages could be useful. This id can also be used to correlate log messages with the output of list scans. Currently the server side scan session object does not track the scan session id. This causes the scan session id to be unavailable for use by listscans and logging during part of the lifecycle of a scan session.

Describe the solution you'd like

Modify the code to always keep track of the scan session id and use the id more in logging.

• [ ] Modify Session class to track session id
• [ ] Update all log messages in SessionManager to include the session id
• [ ] Modify list scans code to ensure session id always shows up. It currently stops showing up for sessions being cleaned up.
• [ ] Test that scan session id is always present in list scans.
• [ ] Improve log messages added in #4840 to include scan session id.
• [ ] Survey log messages related to scans in server and client for places where the scan session id could be included in the log message.

[kevinrr888]

For what version should these changes be made?

[keith-turner]

For what version should these changes be made?

Making these changes in 4.0 would avoid having to deal with merge conflicts.