Change name of second __splink__cluster_count_row_numbered query, prevent table name conflict

[browo097302]

Type of PR

• BUG
• FEAT
• MAINT
• DOC

Is your Pull Request linked to an existing Issue or Pull Request?

#1823

Give a brief description for the solution you have provided

The second query that goes to enqueue __splink__cluster_count_row_numbered has the same name as a query already executed in lines 226 and 232. This leads to a "table already exists" error, so I have simply renamed the last query to __splink__cluster_count_row_numbered_2 as just changing the name was advised in the issue description.

PR Checklist

• Added documentation for changes
• Added feature to example notebooks or tutorial (if appropriate)
• Added tests (if appropriate)
• Updated CHANGELOG.md (if appropriate)
• Made changes based off the latest version of Splink
• Run the linter
• Run the spellchecker (if appropriate)

[ADBond]

Great, thanks!