Meta Issue: Logstash JDBC Integration plugin

[robbavey]

Required before inclusion in Logstash release:

• Create logstash integration github repo
• Integrate git repos
• Remove duplicates
• Ensure project builds and can create gem, integrate gemspec and gradle files
• Update version to be 1 version greater than highest version of existing plugins
• Restrict gemspec to only work Logstash >= 6.5
• Fix unit tests
• Fix integration tests
• Create new changelog
• Organize docs in correct structure(reviewed by @karenzone in [Docs] Refer to individual plugins on doc landing page #9)
• Create proper doc index page ([Docs] Refer to individual plugins on doc landing page #9)
• Publish integration plugin
• Ensure docs build correctly
• Replace references to individual plugins with integration plugin main repo (Replace references to JDBC plugins with integration plugins elastic/logstash#11406)
• Include integration plugin docs in main doc build(Add reference to JDBC integration plugin elastic/logstash-docs#813)
• Ensure that integration plugin docs do not overwrite regular docs for previous releases (Only publish integration plugins that are marked as default elastic/docs-tools#40)
• Manually install and test integration plugins with existing releases:
  • Test clean installation
  • Test installation replaces old individual plugins
  • Test jdbc input functionality
  • Test jdbc static functionality
  • Test jdbc streaming functionality

Other tasks

• Migrate existing/close (and refer to new repo) existing issues and pull requests
• Refactor code to improve reuse across plugins - see (Identify Refactoring Opportunities #5)
• Ensure that integration plugin is kept up to date with changes in individual repos since initial merge.
  • Feature/support prepared statements logstash-filter-jdbc_static#53 - (Porting of prepared statement usage from jdbc static filter #7)
• Update docs, README.md and other files in individual repos

[karenzone]

@karenzone Note to self: Flesh out docs requirements and work with @robbavey to turn this into a template (as we've discussed).