Use wildcard to filter containers on httpstream

Hi -

I'm trying to use logspout in conjunction with kubernetes, and there is no problem with logs being picked up and shipped to the syslog, but with the nature of how containers are named under kubernetes within pods it would be useful if I could apply wildcard matches to httpstream to make it easier to remove the chatter that kubernetes generates. This maybe my misunderstanding what kind of implementation pattern I should be using, but I was thinking along the lines of this commit example - https://github.com/piersharding/logspout/commit/57f25e633b7c0d66f42925ed28970eebf7ed5c61 where I use something like `curl "http://localhost:8000/logs/name:k8s_my_pod*?colors=off"`

Thanks,
Piers Harding.

Start at the httpstream endpoint and review how the existing name filter handles the example URL `logs/name:k8s_my_pod*`. Determine whether wildcard matching should select Kubernetes container names, then verify that matching containers are included while unrelated Kubernetes chatter is excluded.

Written by the indexing model from the issue text.