Fix the regex that identifies if the item is search term for autocomp…

…lete

All digital items that may or may not have type prefixes(like "asset:") are
existing values, the rest are search terms.

When we switched to LinkTargets autocomplete in 6d0b00e, we updated the
regex to handle non-ticket link types like "asset", "articles", etc. The
regex wasn't correct as it treated "foo" in "foo bar" as an existing value,
thus if you selected the ticket from dropdown, the input would be like "foo
123" instead of "123".

share/static/js/autocomplete.js

@@ -167,7 +167,7 @@ window.RT.Autocomplete.bind = function(from) {
                     // remove non-integers in case subject search with spaces in (like "foo bar")
                     var new_terms = [];
                     for ( var i = 0; i < terms.length; i++ ) {
-                        if ( terms[i].match(/^(?:(asset|a|group|user):)\D/) ) {
+                        if ( !terms[i].match(/^(?:(asset|a|group|user):)?\d+$/) ) {
                             break; // Items after the first non-integers are all parts of search string
                         }
                         new_terms.push(terms[i]);