web object browser limits bucket names inconsistently from backend

[nergdron]

ran into an issue earlier today where a user was having a problem deleting a bucket they'd created, because it had a dash in the name. I did some tests and found that the behaviour on bucket naming between the web interface and the uplink backend is inconsistent, uplink allows a lot of reasonable characters while the web interface only allows lowercase latin1, from what I can tell.

we should make the web interface consistent with the wider range allowed on the backend, as most users are going to want things like underscores and dashes and stuff in their bucket names.