Reimplemented LogStash::String setting in Java

[andsel]

Release notes

What does this PR do?

Why is it important/What is the impact to the user?

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files (and/or docker env variables)
• I have added tests that prove my fix is effective or that my feature works

Author's Checklist

• Implements the other constructors, with 2 and 3 params and spread the use
  • Execute SPEC_OPTS="-fd -P logstash-core/spec/logstash/runner_spec.rb" ./gradlew --rerun-tasks :logstash-core:rubyTests there is a problem in reading the deprecation logger messages in

    logstash/logstash-core/spec/logstash/runner_spec.rb

    Line 269 in 467ab3f

    expect(deprecation_logger_stub).to receive(:deprecated).with(a_string_including "`http.host` is a deprecated alias for `api.http.host`")

    . Suggestion mock the Appender and reconfigure logs?
• Check the code for other instantiations of LogStash::String.new
• Translate RSpec tests to JUnit if there are or cover with some testing
• Rename StringSetting to String and use explicit java.lang.String around

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 8ffcede

Failed CI Steps

• :rspec: Ruby unit tests
• :rspec: Ruby unit tests

History

• 💚 Build #1768 succeeded 7a5d6bd
• 💚 Build #1767 succeeded 7590073
• 💔 Build #1721 failed 01f74e7
• 💚 Build #1705 succeeded 6df5df0

cc @andsel