Expose SessionExpirationTimeout is its not at its default value

[nrathaus]

Resolves #19023

[adfoster-r7]

If I remember correctly, each payload can be configured with its own session expiration baked into the payload itself. I think you can also configure each payload to have a new session expiration set at runtime: https://docs.metasploit.com/docs/using-metasploit/advanced/meterpreter/meterpreter-timeout-control.html#changing-timeouts

Therefore I don't think this PR's approach will work by itself without additional changes; We were thinking it'd probably need to be tracked as part of the sysinfo retrieval when Meterpreter is connecting back - and then potentially additionally updated when the user updates the value via the console in some way. For instance - I don't think we'd want to make fresh RPC calls to Meterpreter for each sessions -v / session -x call

[github-actions]

Thanks for your contribution to Metasploit Framework! We've looked at this pull request, and we agree that it seems like a good addition to Metasploit, but it looks like it is not quite ready to land. We've labeled it attic and closed it for now.

What does this generally mean? It could be one or more of several things:

• It doesn't look like there has been any activity on this pull request in a while
• We may not have the proper access or equipment to test this pull request, or the contributor doesn't have time to work on it right now.
• Sometimes the implementation isn't quite right and a different approach is necessary.

We would love to land this pull request when it's ready. If you have a chance to address all comments, we would be happy to reopen and discuss how to merge this!