[juniper_srx] Improve TCP input

[taylor-swanson]

What does this PR do?

• Add TLS support to TCP input
• Add custom TCP options support

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.

How to test this PR locally

cd packages/juniper_srx && elastic-package test

Related issues

• Relates Firewall Integration Input Consistency  #1878

Screenshots

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-05-12T07:54:55.884+0000

• Duration: 18 min 5 sec

Test stats 🧪

Test	Results
Failed	0
Passed	13
Skipped	0
Total	13

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (1/1)	💚
Files	100.0% (7/7)	💚 3.597
Classes	100.0% (7/7)	💚 3.597
Methods	100.0% (50/50)	💚 11.753
Lines	70.799% (1525/2154)	👎 -18.314
Conditionals	100.0% (0/0)	💚

[elasticmachine]

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

[efd6]

Will there be a TLS test?

[taylor-swanson]

Will there be a TLS test?

I thought about it originally and was overthinking the complexity of setting that up. I just tested it and it turns out it's trivial to set up and hard code the cert/key pair (we won't test validating certificates). I'll add a TLS test here and to the other packages as well.

[taylor-swanson]

TLS test has been added.