Duplicate key __pfn_input_topic__ in presto server

[pointearth]

Motivation

When I query a topic with presto
`presto> select * from xxxTable from pulsar."xxxTenant/xxxNamespace"."last-topic-value";

Query 20210222_101426_00019_jvnf5, FAILED, 2 nodes
Splits: 18 total, 0 done (0.00%)
0.79 [0 rows, 0B] [0 rows/s, 0B/s]

You can see it cast a long time, and will not stop.
And you can see many error messages in presto server:
Query 20210222_101426_00019_jvnf5 failed: Duplicate key pfn_input_topic (attempted merging values persistent://first-tenant-value/first-namespace-value/first-topic-value and persistent://second-tenant-value/second-namespace-value/second-topic-valu)`

To Reproduce
Steps to reproduce the behavior:
In pulsar version before 2.7.0

1. create 3 topics: first-topic-value, second-topic-value, last-topic-value
2. create 2 pulsar functions, f1 pulls messages from first-topic-value, writes to second-topic-value, f2 pulls messages from second-topic-value, writes to last-topic-value.
3. In all pulsar version (2.7.0 as newest currently)`presto> select * from xxxTable from pulsar."xxxTenant/xxxNamespace"."last-topic-value";
4. See these errors

Expected behavior
query successfully, and No error.

Screenshots

Desktop (please complete the following information):

• OS: CentOS , pulsar 2.7.0

Additional Information###

presto can't run in the ruined data came from old pulsar funcations.

Modifications

if key dumplicated, use new one.

Verifying this change

This change added tests and can be verified as follows:

• Added unit test in RawMessageImplTest.java

Does this pull request potentially affect one of the following parts:

If yes was chosen, please highlight the changes

• Dependencies (does it add or upgrade a dependency): (yes / no)
• The public API: (yes / no)
• The schema: (yes / no / don't know)
• The default values of configurations: (yes / no)
• The wire protocol: (yes / no)
• The rest endpoints: (yes / no)
• The admin cli options: (yes / no)
• Anything that affects deployment: (yes / no / don't know)

Documentation

• Does this pull request introduces a new feature? (yes / no)
• If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
• If a feature is not applicable for documentation, explain why? it is a bug
• If a feature is not documented yet in this PR, please create a followup issue for adding the documentation
• It is just like <fix duplicate key to send propertys #6390>, but it causes presto issue.

[pointearth]

@codelipenghui please review the code.

[sijie]

@pointearth Great contribution!