Bump astroid from 1.5.3 to 2.3.3

[dependabot-preview]

Bumps astroid from 1.5.3 to 2.3.3.

Changelog

Sourced from astroid's changelog.

What's New in astroid 2.3.3?

Release Date: 2019-11-06

• Relaxed six dependency.

What's New in astroid 2.3.2?

Release Date: 2019-10-18

• All type comments have as parent the corresponding astroid node

  Until now they had as parent the builtin ast node which meant
  we were operating with primitive objects instead of our own.

  Close PyCQA/pylint#3174

• Pass an inference context to metaclass() when inferring an object type

  This should prevent a bunch of recursion errors happening in pylint.
  Also refactor the inference of IfExp nodes to use separate contexts
  for each potential branch.

  Close PyCQA/pylint#3152
  Close PyCQA/pylint#3159

What's New in astroid 2.3.1?

Release Date: 2019-09-30

• A transform for the builtin dataclasses module was added.

  This should address various dataclasses issues that were surfaced
  even more after the release of pylint 2.4.0.
  In the previous versions of astroid, annotated assign nodes were
  allowed to be retrieved via getattr() but that no longer happens
  with the latest astroid release, as those attribute are not actual
  attributes, but rather virtual ones, thus an operation such as getattr()
  does not make sense for them.

• Update attr brain to partly understand annotated attributes

  Close #656

What's New in astroid 2.3.0?

... (truncated)

Commits

• ace7b29 Prepare 2.3.3
• d5937ef Update six version to 1.13 (#719)
• 8b0fcc2 Prepare 2.3.2
• cdb4472 Fix lint warnings
• ed42e0c Pass an inference context to metaclass() when inferring an object type
• 0088cc0 Bump the branch to 2.3.2
• 5f235c0 All type comments have as parent the corresponding astroid node
• 609f130 Update travis credentials
• 09d561c Prepare 2.3.1
• a9d640d Add the env parameter to subprocess.check_output
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)