fix: omit double quotes from connection name

[pokedpeter]

When passing connection name parameter, connection name includes double quotes, so omit them

fix #947

🔗 Linked issue

#947

❓ Type of change

• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Some Ace migration commands pass the connection name parameter to other commands including double quotes, which results in an error.

This fix excludes the double quotes when passing through the connection name string.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[pokedpeter]

One of the PR checks failed due to a failed npm install. Couldn't see a way to trigger the checks again.

[RomainLanz]

Thanks!

[thetutlage]

It will be nice to have tests alongside it, because looking at the issue, I see the connection name already had double quotes and since wrapping it inside double quotes again caused the issue.

But ideally, there shouldn't been any double quotes in first place.

So let's have tests around it.