Better autocomplete support for components

Summary

The autocomplete behaviour for components is limited and should provide more options.

Steps to Reproduce

When creating or editing an issue, the search works from the first letter of a word in the component. As an example, please refer below:

Component name: Component One
Component name: Component-Two

1. Component One has two words; thus typing c or o will show it.
2. Component-Two is treated as one word; thus typing only c will show it.

Expected Results

1. For Component One and Component-Two, typing any letter (in the component) should show it (plus any other components with the letter). The component options should narrow down as more letters are typed.

Actual Results

1. For Component One, typing c or o will show it.
2. For, Component-Two, typing only c will show it.

Note from a customer:

I notice that Component and Label both behave the way you described.
However, Epic behaves differently (and this is the behaviour I would prefer Component and Label to have). For example, if I have an epic named ews-client-python, autocomplete will suggest it if I type "p" in the Epic field. In fact, it will even auto-suggest ewsClientPython.