[Feature] Configurable set of project keys to detect as inline issues without needing `JIRA:` prefix

[strazto]

Is your feature request related to a problem? Please describe.

• I find typing out the JIRA: prefix quite clunky, especially when it always precedes a jira key which has its own clunky encoding, for example:
  • I don't like typing JIRA:PROJECT2-123
  • I don't like reading JIRA:PROJECT2-123 in plaintext either
  • I already know PROJECT2-\d+ is going to be a jira issue, and I want it to render as an inline issue

Describe the solution you'd like

For some project keys / issue keys, it'd be great to just automatically encode it as a jira key if it matches a pattern / is within a list, for example, some config of the following structures:

auto_inline_project_keys:
# maybe regex, maybe not - i dont know
  - PROJECT2
  # regex example
  - PRJ\d

Maybe also some supporting options about when this shouldn't be applied, or how to mark it to show as "compact", something like:

auto_inline_project_keys:
  - key: PROJECT2
    modifiers:
    - default: compact
    # Don't apply inlining if wrapped in square brackets, eg [PROJECT2-123]
    - square_brackets: disable
    # Full display if wrapped in parens eg (PROJECT2-123)
    - parentheses: full

Describe alternatives you've considered

• configuring a shorter prefix string, like J: , eg J:PROJECT2-123.
  • Quicker to type, but less readable / clear what its for when reading plaintext

Additional context
NA

• Check the existing feature request and vote with a 👍 the one you like
  • I don't see anything that matches this request