Specify the key module requirement in the composer.json with a caret symbol instead of hardcoding to a specific one

Problem/Motivation

Right now the module is hardcoded to the 1.19 version of drupal/key. This means if the module will have updates, then we cannot update to it until this module puts out a new version with updated dependencies. Using semantic versioning updating to a new minor should not break compatibility, so the best practice would be specifying version 1 of the key module like this:

        "drupal/key": "^1.19"

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes