Description update with `jira edit` send markdown without transformation to jira markup lang

[snpefk]

Describe the bug Can't update custom field "Fix build".

Please provide following details

1. JiraCLI Version:

   # wierd output, AUR package says that it's "jira-cli-1.2.0-1"
   (Version="v0.0.0-dev", GitCommit="", CommitDate="", GoVersion="go1.19.4", Compiler="gc", Platform="linux/amd64") 
   

2. Are you using Jira cloud or on-premise jira server?

   SERVER INFO
   -----------
   
   Version: 	 8.22.0
   Build Number: 	 822000
   Deployment Type: Server
   Default Locale:  
   
   

3. What operating system are you using? Also mention version.

   Linux 5.15.86-1-MANJARO 
   

4. What terminal are you using? Also mention version.

   alacritty 0.11.0 (8dbaa0bb)
   

To Reproduce

Steps to reproduce the behavior:

1. Create jira issue with empty description
2. Update description with jira issue edit CORE-1000
3. Write text in markdown & send

Expected behavior Jira Issue text properly formatted: links rendered as links, not [google](https://google.com, code block looks like block code

Screenshots Sorry

Additional context Nothing

[icepuma]

Hey, I stumbled upon the same problem today. I have a workaround in place to ensure commonmark is used when creating an issue and "jira flavoured markdown" when editing one. I would contribute the code. I could think of a second parameter --body-without-markdown-conversion (or a more suitable name) in both (create/edit) cases which overrules --body in the edit case and --template & --body in the creation case. This would break the behaviour for edit, but not for create. Then we could make the --body behaviour for edit like in create where a conversion takes place.

Or we introduce a complete new set of params e.g. --rich-description (does the conversion) and --description (takes the text "as is") which are used in both cases.