I do understand your feelings. However, you seem to be overvaluing the importance of having the plugin published in the Plugins directory. I can't see any recent commit to your plugin's repository. Why not to use the time while the plugin is waiting for the approval check and just continue improving the code?
- There was a new Moodle version 3.8 released. Why not to re-test the plugin with the new version and update the list of supported versions or eventually release a new version of the plugin.
- There were some coding style violations detected and reported on your plugin's page. This is a perfect opportunity to fix them all and release a new version with green checks.
- You can re-check all the points at the plugin contribution checklist and make sure you haven't missed any. For example, the plugin does not have the privacy API implemented. It is not a requirement for having it approved, but it is still a missing essential feature.
- You could announce the availability of the plugin in the General plugins forum to eventually receive some early feedback from the community. Folks can download and test your plugin from Github and you might get the opportunity to provide support by answering eventual questions.
There are many things you can already do to promote and support your plugin even while it is still waiting (together with 83 others) for the formal approval. That would better illustrate and prove your actual interest and commitment to provide a longitudinal support and maintenance of your plugin. The approval itself is just a tiny step in a long journey.
There's no need to worry. From what I was able to see while skimming the code at Github, it seems to be well written plugin and I believe there will be nothing blocking the approval.
I am sorry for your demotivation (and believe me, I know how it tastes). I just can't see any reason to put hands off your plugin just because it was not approved yet.