MEC021: Minor issue on subscription expiration

Creating a subscription to the AMS notification with an expiry deadline before the current date and time results in the successful creation of the subscription. Below is an example, whose expiry date in before the current date and time.

{
    "callbackReference": "http://example.com/callback",
    "requestTestNotification": false,
    "websockNotifConfig": {
        "websocketUri": "ws://example.com/websocket",
        "requestWebsocketUri": true
    },
    "expiryDeadline": {
        **"seconds": 207735360,**
        "nanoSeconds": 0
    },
    "filterCriteria": {
        "appInstanceId": "ca29c5a5-f471-4098-abcb-d55d83410087"
    },
    "subscriptionType": "MobilityProcedureSubscription"
}

As a response, the subscription payload is returned, along with the 201 HTTP Code and the subscription ID. However, using this subscription ID for querying the just-created subscription returns 404 Not found. Suggest checking the logic on processing the expiryDeadline during the subscription creation stage.