Bump concurrent-ruby from 1.1.4 to 1.1.5 in /docs

[dependabot-preview]

Bumps concurrent-ruby from 1.1.4 to 1.1.5.

Release notes

Sourced from concurrent-ruby's releases.

Extension Gem Pre-release 3

A private release used to fix and test pre-compiled extensions for Windows. It was never pushed to Rubygems.

Extension Gem Pre-release 2

This release builds two gems from this repo: concurrent-ruby and concurrent-ruby-ext, the latter of which contains the C-native extensions that were added to the core gem in the 0.7 release.

• Background describing why we're making this change: [New Approach to C/Java Native Extensions #186](https://github-redirect.dependabot.com/ruby-concurrency/concurrent-ruby/issues/186)
• The PR from which this pre-release was created: [Builds two gems from one repo. #205](https://github-redirect.dependabot.com/ruby-concurrency/concurrent-ruby/pull/205)
• A prior attempt to to create two gems from two separate repos (rejected): [Moved C extensions into a companion gem. #197](https://github-redirect.dependabot.com/ruby-concurrency/concurrent-ruby/pull/197)

Changelog

Sourced from concurrent-ruby's changelog.

Release v1.1.5, edge v0.5.0 (10 mar 2019)

concurrent-ruby:

• fix potential leak of context on JRuby and Java 7

concurrent-ruby-edge:

• Add finalized Concurrent::Cancellation
• Add finalized Concurrent::Throttle
• Add finalized Concurrent::Promises::Channel
• Add new Concurrent::ErlangActor

Commits

• ffed3c3 Doc update
• 3b203a7 Clarify ErlangActor requirements
• f72141e Merge pull request #791 from ruby-concurrency/ruby-association
• 3ff1cb0 Bump version, update doc
• d84d13e Fix spec timing
• 04e9390 Add missing AbstractStruct.[] alias for new
• fe386d4 Fix edge version definition placement
• 2307958 Merge pull request #804 from cavinkwon/add_respond_to_missing_to_async
• c1f6a17 Add respond_to_missing? for async/await
• b4b0542 Merge pull request #803 from grosser/grosser/source
• 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 ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major 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)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.