Pull Request Description

This pull request fixes a bug that occurs when using ">[!" (without a space between ">" and "[") instead of "> [!".

Changes Proposed

• In the testAndReturnQuery function, prefix and query groups were created during matching, enabling cursor movement without using an offset.
• So, we removed the unnecessary offset variable.
• In the AdmonitionSuggest class, when selecting a suggestion after "```ad-", modified it so that the cursor moves to the position after the text.
• Refactored the code, because "this.context" was used a lot.

Related Issues

Fixes #339 ( Strange Behavior of Callout Type Autocompletion )

Checklist

• I have read the contribution guidelines and code of conduct.
• I have tested the changes locally and they are working as expected.
• I have added appropriate comments and documentation for the code changes.
• My code follows the coding style and standards of this project.
• I have rebased my branch on the latest main (or master) branch.
• All tests (if applicable) have passed successfully.
• I have run linters and fixed any issues.
• I have checked for any potential security issues or vulnerabilities.

Screenshots (if applicable)

1. Confirmed that ">[!n" works as expected when entered.
   
   

2. Confirmed that when entering ">[!", there is no line break and works as expected.
   
   

3. In the case of ">[! ", since \w follows in the regular expression, spaces were not considered.

4. Additionally, in the case of "```ad-", where the cursor was after the -, we adjusted it to move to the end of the text.
   

(before)

(after)

Additional Notes

This is my second time creating a Pull requests, so it might not be perfect.
If I made any mistakes, I would appreciate it if you could let me know.
Thank you. 🍭