Refactor out Dir.glob from ActionDispatch::Static

Refactor out Dir.glob from ActionDispatch::Static

Dir.glob can be a security concern. The original use was to provide logic of fallback files. Example a request to `/` should render the file from `/public/index.html`. We can replace the dir glob with the specific logic it represents. The glob {,index,index.html} will look for the current path, then in the directory of the path with index file and then in the directory of the path with index.html. This PR replaces the glob logic by manually checking each potential match. Best case scenario this results in one less file API request, worst case, this has one more file API request.

Related to #16464

Update: added a test for when a file of a given name (`public/bar.html` and a directory `public/bar` both exist in the same root directory). Changed logic to accommodate this scenario.
It is adding a test for previous behavior. The behavior was intentional, look at the glob matchin pattern. If bar.html does not exist then bar/index.html should be rendered. 

I don't know if the prior behavior was based off of a spec but it has been around for years.