[places] Setting reverse geocoding BottomSheetBehavior hideable to true

[langsmith]

Resolves #908 by adjusting the Places Plugin's BottomSheetBehavior.

cc @orlikraf, who had a helpful comment at #908 (comment)

[langsmith]

The crash that was happening

2020-03-19 00:16:06.986 9832-9832/? E/AndroidRuntime: FATAL EXCEPTION: main
    Process: com.mapbox.mapboxandroiddemo.debug, PID: 9832
    java.lang.IllegalArgumentException: Illegal state argument: 5
        at com.google.android.material.bottomsheet.BottomSheetBehavior.startSettlingAnimation(BottomSheetBehavior.java:1099)

Discussions about java.lang.IllegalArgumentException: Illegal state argument: 5:

• https://stackoverflow.com/a/47871634/6358488
• https://stackoverflow.com/a/53263494/6358488

[langsmith]

[orlikraf]

Resolves #908 by adjusting the Places Plugin's BottomSheetBehavior setHideable() value. I don't believe there's any downside to hardcoding the fact that the sheet can be hideable.

cc @orlikraf, who had a helpful comment at #908 (comment)

@langsmith
If I recall correctly a hideable BottomSheet can be dismissed out of screen with a swipe down without a way to swipe it into view again. I'm 90% sure about this so please check it yourself.

I would suggest to call isShowing only once before setting hideable and use the result in both later calls.

[langsmith]

I would suggest to call isShowing only once before setting hideable and use the result in both later calls.

Thanks @orlikraf , that's what I'm now doing in this pr. Getting a weird CI 🐛 now.

[langsmith]

CircleCI 💥 is from a Mapbox infrastructure 🐛 , rather than something with this pr's code changes.