Fixing log presentation

[Clearmist]

Regarding issue #5

• The copyright container is no longer squished on smaller width displays.
• Fixed some React warnings about missing keys in some maps.
• Clicking the mouse around while a log was showing was also moving the map because the log element was being drawn within the map container. I moved the log element to the page container.
• The new log element also uses the full page width, is responsive on smaller displays, and has a semi-transparent modal background.
• The close button now has a hover style and pointer cursor to better show it's clickable.

One remaining issue that I left in is the text of the logs. Because we're using pre elements white-space doesn't wrap by default. We should adjust the CSS white-space property to wrap the text or replace the pre elements with p and a terminal-like font. Although, React doesn't want you to insert elements into text like that so .replace() may not work in this way so adjusting the white-space is probably the best option.

[Clearmist]

My second commit is adding a new map layer with leaflet tooltips styled in such a way that they resemble region names. I couldn't add these in the official way because it involves learning how to make WMS map layer data and that's way too much to learn. It would also include rendering new map images for each zoom level that include the region names which would increase bandwidth requirements to use this map.

Within App.css:57 I have left a semi-transparent background style in case you like that look better. Here is a comparison. I committed using the transparent background (bottom image).

[BrookJeynes]

@Clearmist in regards to this:

One remaining issue that I left in is the text of the logs. Because we're using pre elements white-space doesn't wrap by default.

One thing we could do is pass in a list for each text paragraph? Then we would just add each item in the list as it's own p element (and change to a more terminal font). What do you think about this?

[Clearmist]

That would work, I just didn't want to adjust the format of your json file without your permission. 😁