Figure out if and why we should install chardet

[consideRatio]

I think we need to get to the bottom of if and why we should install chardet explicitly, and if so, what version we should constrain it to. Below are some reasons.

• the-littlest-jupyterhub/tljh/installer.py

  Lines 131 to 145 in c6c6e34

  	conda.ensure_pip_packages(
  	prefix,
  	[
  	"jupyterhub==1.4.0",
  	"jupyterhub-dummyauthenticator==0.3.1",
  	"jupyterhub-systemdspawner==0.15",
  	"jupyterhub-firstuseauthenticator==0.14.1",
  	"jupyterhub-nativeauthenticator==0.0.7",
  	"jupyterhub-ldapauthenticator==1.3.0",
  	"jupyterhub-tmpauthenticator==0.6",
  	"oauthenticator==0.10.0",
  	"jupyterhub-idle-culler==1.0",
  	"chardet==3.0.4",
  	"git+https://github.com/yuvipanda/jupyterhub-configurator@317759e17c8e48de1b1352b836dac2a230536dba"
  	],

• Install error Ubuntu 20.04 header pyconfig.h not found #708 - A failure related to chardet==3.0.4
• tljh-config ContextualVersionConflict - chardet 4 vs jupyterhub-traefik-proxy #642 - A failure related to chardet version 4, and a comment about its pinning: Bump to recent versions, and make bootstrap.py update to those when run #719 (comment)
• traefik-proxy unpinned aiohttp, which requires chardet of a certain version: https://github.com/jupyterhub/traefik-proxy/pull/115/files#diff-4d7c51b1efe9043e44439a949dfd92e5827321b34082903477fd04876edb7552
• From Bring TLJH up to date 2i2c-org/upstream#17 I read:

  jupyterhub-traefik-proxyhas aiohttp pinned to an older version so that it works with the consul python client. However, this pin clashed with chardet latest version and impacted tljh-configfunctionality and has been fixed by pinning thechardetversion.

My guess, quite confused about things still, is that we could stop using a pin of chardet in tljh.