I maintain that it's a duplicate. We don't need a different question for getting xdebug working in every possible IDE or environment, we need the generic steps for all IDEs and environments, which we have. From there, each user can apply the knowledge to the software they've chosen to use, with whatever caveats/additional steps come with that decision. It will likely involve consulting the manual for said software.
However I'm not infallible, so if you really think that it's a different question, where are the details that show it? For your research, we have:
I reviewed a lot of articles
With respect: so what? What did they say? What, specifically, did you try from these articles? What happened? What errors did you get? How do we know you didn't just follow the existing instructions incorrectly or make a typo etc? The methods outlined in the duplicate work with every other IDE, what does your research about your IDE tell you about this? You can't be the only one who's ever had trouble connecting this IDE to xdebug using CLI, what has your research into that told you? How do other people connect non-Drupal CLI projects to this IDE?
And so on.
And on to your ultimate question:
This isn't a help desk so no, unless there's a specific question, no help. If you ask a vague, generic question, and the same vague, generic question exists with good answers, closing it as a duplicate is the right thing to do.
If your question is sufficiently different, or the answers didn't help you, you need to be very specific about what steps you took to apply those solutions. That way people can spot if you've just done something obviously wrong, or if your question really does come into new territory.
So to answer your question directly:
How to show moderators that I have enough knowledge to understand those answers?
Easy. Actually show it, by describing how you applied it, and why it didn't help solve the problem.