Support setting Due Date on issues

[control-d]

Please add support for setting the Due Date (system duedate field).

curl -s "https://server.example.com/rest/api/2/issue/createmeta?projectKeys=ISSUE&expand=projects.issuetypes.fields" -H "Authorization: Bearer $JIRA_API_TOKEN" | jq .
[...]
            "duedate": {
              "required": false,
              "schema": {
                "type": "date",
                "system": "duedate"
              },
              "name": "Due Date",
              "fieldId": "duedate",
              "hasDefaultValue": false,
              "operations": [
                "set"
              ]
            },

It is possible to create/update this field via the API

$ curl -H "Authorization: Bearer $JIRA_API_TOKEN" -H "Content-type: application/json" -H "Accept: application/json" -d"{\"fields\":{\"duedate\":\"2023-01-26\"}}" -X PUT https://server.example.com/rest/api/2/issue/ISSUE-123 -w '%{response_code}\n'
204

but it doesn't seem possible to set using jira-cli. It's not available as standard metadata, and referencing it doesn't work

~ # jira serverinfo

SERVER INFO
-----------

Version: 	 8.20.11
Build Number: 	 820011
Deployment Type: Server
Default Locale:  

~ # jira issue edit ISSUE-123 --custom duedate="2023-01-26" --no-input
⠋ Updating an issue...
Some custom fields are not configured and will be ignored. This will fail with error in the future release.
Please make sure that the passed custom fields are valid and configured accordingly in the config file.
Invalid custom fields used in the command: duedate

✓ Issue updated

If I manually add it to ~/.config/.jira/.config.yml in a certain way it does start to work. Here's the config:

           - name: Due Date           
              key: duedate 
              schema:          
                datatype: date

This seems to override the CLI key to due-date

~ # jira issue edit ISSUE-123 --custom due-date="23-01-30" --no-input

✓ Issue updated
https://server.example.com/browse/ISSUE-123

The Due Date does get updated, Here's more examples:

~ # jira issue edit ISSUE-123 --custom due-date="2023-01-20" --no-input

✓ Issue updated
https://server.example.com/browse/ISSUE-123

$ curl -s "https://server.example.com/rest/api/2/issue/ISSUE-123" -H "Authorization: Bearer $JIRA_API_TOKEN" | jq .fields.duedate
"2023-01-20"

~ # jira issue edit ISSUE-123 --custom due-date="2023-01-30" --no-input

✓ Issue updated
https://server.example.com/browse/ISSUE-123

$ curl -s "https://server.example.com/rest/api/2/issue/ISSUE-123" -H "Authorization: Bearer $JIRA_API_TOKEN" | jq .fields.duedate
"2023-01-30"

but it would be nice to get something like --duedate as an option.