Fixed shipper cache to include output type in the key

[girodav]

What does this PR do?

With the addition of Logstash as output, we might have multiple outputs defined for one input. This needs to be considered in the key space for shipper_cache

Why is it important?

If a user has a configuration like

inputs:
  - type: s3-sqs
    id: arn:aws:sqs:eu-central-1:627286350134:test-esf-sqs-s3
    json_content_type: disabled
    outputs:
      - type: logstash
        [etc]
      - type: elasticsearch
        [etc]

Shipper cache would include only one entry for arn:aws:sqs:eu-central-1:627286350134:test-esf-sqs-s3, instead of one of logstash and one for elasticsearch, if both shippers fail

[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: 2023-02-16T14:07:10.144+0000

• Duration: 59 min 31 sec

Test stats 🧪

Test	Results
Failed	0
Passed	434
Skipped	0
Total	434

🤖 GitHub comments

Expand to view the 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% (5/5)	💚
Files	100.0% (32/32)	💚
Classes	100.0% (32/32)	💚
Lines	100.0% (2207/2207)	💚
Conditionals	100.0% (760/760)	💚

[girodav]

/test