Update of deck-gl versions to 8.9.34 with fixed CI and drop EOL Python 3.6 and 3.7

[graingert-coef]

About

this is #20 with my changes that fix CI and an update to deck.gl 8.9.34

Description of changes

Pre-Merge checklist

• The project was correctly built with npm run build.
• If there was any conflict, it was solved correctly.
• All changes were documented in CHANGELOG.md.
• All tests on CircleCI have passed.
• All Percy visual changes have been approved.
• Two people have 💃'd the pull request. You can be one of these people if you are a Dash Deck core contributor.

Reference Issues

Closes #[issue number]

Other comments

[alexcjohnson]

Hmm ''DeckGL isn't going to work. Somehow that's coming from --r-prefix '' in the build:py_and_r package script. Either we should figure out how to fix this (get it back to just deckGL (somehow this PR is updating that as well?) and delete the files that reference ''DeckGL) or, more likely, since we're not really supporting Dash for R at this point, just remove --r-prefix '' from that command and delete all the R artifacts (R/, inst/deps/, man/, DESCRIPTION, NAMESPACE entirely.

For that matter it'd be great to remove and .gitignore the Python build artifacts as well (all the contents of dash_deck/ except for __init__.py, but that's not a big deal, we can leave that for now. We used to commit build artifacts so people could install directly from the repo, but in most projects we stopped doing that long ago.

[graingert-coef]

I deleted the R and man directories and reran npm run build I think the spurious '' was as a result of @vogt31337 running build:py_and_r on windows. I ran the script from macos and it created the correct files.

I'd like to keep R support and built files in this PR as we're currently deploying our app by installing directly from the repo referencing this branch. I'll delete the built files in a new PR if you'd like

[alexcjohnson]

Got it - that all makes sense. I know we have various issues with Windows, as none of our core devs use it so we rely on the community to help find and resolve bugs when running there (see eg plotly/dash#2752)

Does that mean you're using this with Dash for R? That's great if so, just curious, we don't always know which of our packages people actually use!

[alexcjohnson]

💃 Beautiful!

[alexcjohnson]

@graingert-coef FYI, I was about to make a release (tentatively 0.1.0 but I'm tempted to call it 1.0.0 if we get it fully working) but noticed some errors running demos/usage-events.py:

I didn't try with just this PR so it's possible #26 caused this, though that one should be fairly uncontroversial. My hunch is the structure of certain events got more complex with the new deck.gl version, but it's not clear to me which events are causing this. I also haven't tried any of the other demo apps yet. v0.0.1 does not have this issue.