Update search by place name based on user feedback.

[Mike-Heneghan]

Feedback from users suggests the inclusion of the postcode in brackets after a placename in the dropdown can be confusing for users. Additionally when the postcode in the field is exchanged for a postcode in can be confusing.

Although it needs to be clear to users that when they search by placename we assign a postcode to be used for the search.

This could be communicated with explanatory test i.e. Help and support in Edinburgh (EH1 1BQ).

[Mike-Heneghan]

Removed the bracketed postcode from after the placename although on click or enter still changes to the postcode.

[Mike-Heneghan]

Updated the JS so that when an option is selected it autocompletes to the place_name this change also applies to situations where the user doesn't select an option but hits enter or clicks search.

Now the placename is searched found to be an invalid postcode, it is checked for being a placename in which case the user is redirected to the search results with that postcode.

In this situation, the user would have the effect of seeing a postcode instead of the term they searched.

To allow the redirect or the search to have the placename in the form of Glasgow (G2 4AA ) it would be necessary to add another argument for the searched placename.

[Mike-Heneghan]

When redirecting from search with an invalid postcode but a valid place_name added the place_name kwarg and a conditional in the template to render a slightly different results header.

This shows the searched place but also has the postcode in a way that would hopefully reassure the user there search was interpreted correctly but give the context of the postcode being used

[Mike-Heneghan]

Suggested improvement that on selecting the dropdown option search starts immediately.

[Mike-Heneghan]

Merged