Rampart interop: SecureConversation session for session expired

**The problem:**
Axis2 Rampart issued SecureConversation tokens expire after 5 minutes, however, it doesn't support SC token renewal. WSIT is unable to handle this situation even when renewExpiredSCT=false. Specifying Lifetime also doesn't work because Rampart ignores the client-supplied lifetime and uses its own (This is not illegal)

**What should happen:**
When SCT is expired and renewExpiredSCT is false, a new SCT should be requested and a new SC context should be established.

**What happens instead:**
WSIT throws a WSSecureConversationException: SecureConversation session for session Id: xxxx has expired.
It is then impossible to recover from this condition without restarting the application.
#### Environment
Client: WSIT 2.1
Server: Axis2 Rampart 1.5
WS-Policy: SymmetricBinding SecureConversation
#### Affected Versions
[2.1]

Source: [https://github.com/javaee/metro-wsit/issues/1539](https://github.com/javaee/metro-wsit/issues/1539)
Author: glassfishrobot

No source file, test, or entry point is named. Start by reproducing the expired SecureConversation session with WSIT 2.1 and Axis2 Rampart 1.5, then trace the WSSecureConversationException path. Done means an expired SCT with renewExpiredSCT=false requests a new SCT and establishes a new SC context without restarting the application.

Written by the indexing model from the issue text.