fix(trouble-nvim): prevent clashes with existing <Leader>x mappings

[rami3l]

📑 Description

This is to avoid clashes with the recent addition of <Leader>x to AstroNvim.

This PR has also simplified some mapping descriptions.

[github-actions]

Review Checklist

Does this PR follow the [Contribution Guidelines](development guidelines)? Following is a partial checklist:

Proper conventional commit scoping:

• If you are adding a new plugin, the scope would be the name of the category it is being added into. ex. feat(utility): added noice.nvim plugin

• If you are modifying a pre-existing plugin or pack, the scope would be the name of the plugin folder. ex. fix(noice-nvim): fix LSP handler error

• Pull request title has the appropriate conventional commit type and scope where the scope is the name of the pre-existing directory in the project as described above

• README is properly formatted and uses fenced in links with <url> unless they are inside a [title](url)

• Entry returns a single plugin spec with the new plugin as the only top level spec (not applicable for recipes or packs).

• Proper usage of opts table rather than setting things up with the config function.

• Proper usage of specs table for all specs that are not dependencies of a given plugin (not applicable for recipes or packs).

[mehalter]

We can leave all the mappings as is, just change <Leader>xq to <Leader>xQ and <Leader>xl to <Leader>xL

[mehalter]

No need to make them all 3 key presses when they can share the Quickfix/Lists menu

[rami3l]

We can leave all the mappings as is, just change <Leader>xq to <Leader>xQ and <Leader>xl to <Leader>xL

@mehalter Thanks for your suggestion! I'll modify my PR accordingly.

[rami3l]

We can leave all the mappings as is, just change <Leader>xq to <Leader>xQ and <Leader>xl to <Leader>xL

@mehalter What if other types of Quickfix/Lists show up later though? Looks like we are prioritizing trouble somehow, although that would be beneficial for my own usecase...

[mehalter]

Yeah I think if the user adds several list plugins it can just be up to them the priority they want

[rami3l]

Yeah I think if the user adds several list plugins it can just be up to them the priority they want

@mehalter Okay, I've applied your suggestions. One problem I have is that the original descriptions are too long, so I've tried my best to shorten them a bit.

[mehalter]

We should leave the original messages no? That mention Trouble?

[mehalter]

@rami3l this should be a 2 character change PR

[mehalter]

Ah I see your most recent comment now

[mehalter]

Sure! Looks good

[rami3l]

Sure! Looks good

@mehalter Thanks a lot, and sorry for the previous confusion! 🙇