Suggest API - bugs with encoding multiple levels of geo precision.

1) One issue reported by a user is due to the truncation of the geohash string. Added YAML test for this scenario
2) Another suspect piece of code was the “toAutomaton” method that only merged the first of possibly many precisions into the result.

Closes #7368
I started down that route but the Java API looked to be missing the "context" part of the suggest API - I can roll a change for that into this PR if you want.