[QA] Key mismatch for expiration date in feature file and implementation

[grgprarup]

When (send|create)ing the shares key expirationDateTime is used in the request body.

In the feature file expireDate and expirationDateTime is used

When user "Alice" sends the following resource share invitation using the Graph API:
      | resource        | <resource>               |
      | space           | Personal                 |
      | sharee          | grp1                     |
      | shareType       | group                    |
      | permissionsRole | <permissions-role>       |
      | expireDate      | 2043-07-15T14:00:00.000Z |

And user "Alice" has sent the following resource share invitation:
      | resource           | testfile.txt         |
      | space              | Personal             |
      | sharee             | Brian                |
      | shareType          | user                 |
      | permissionsRole    | Viewer               |
      | expirationDateTime | 2025-07-15T14:00:00Z |

(space share also)

both of the steps use sendShareInvitation and the implementation of sendShareInvitation uses expireDate so the share step with expirationDateTime creates a share without an expiration date as it sends null.

• Use expirationDateTime for sharing graph API step (feature + implementation)
• Keep expireDate for sharing API steps (not to change)