First, from the comments here:
Not attempting to answer the question, that is not very helpful as all.
This is a completely wrong mindset for using Stack Overflow. The way we help is not by "attempting to answer the question" regardless of quality. That is a service provided by a discussion forum or a help center, and Stack Overflow is not those things. If you would prefer to "help" people in such an environment, there are countless such places all over the internet, and you are welcome to use them.
But at Stack Overflow, as described in the tour, we are working to build a usable, searchable reference library. People are helped when they find a relevant Q&A on Stack Overflow using a search engine, and therefore don't have to ask. Asking directly is, in essence, a bug report against Stack Overflow claiming that the site lacks a question it should have.
If I took that approach there would be no answers at all around Cucumber.
Nothing prevents you, and in fact it is encouraged to share your knowledge by asking a question that does meet quality standards, just to have a place to put the appropriate answer. Especially if it covers a problem that happens all the time, but only to beginners who cannot ask a good question.
Thus, we can now understand:
I wrote an answer to a poorly written question.
This was your first mistake. If you think information is missing from a question then you should vote to close it rather than attempting to write an answer. You were given the privilege, over 7k reputation ago, for a reason: your experience is supposed to have trained you to recognize the site's standards and appreciate the value of upholding them.
And the only way to find the actual root cause would be to create an MCVE.
In other words, the question was missing an MCVE, when it required one. That is a textbook case for the Needs Debugging Details closure reason.
As an aside: please also do not add a second answer to a question in order to point out a totally separate problem from what you pointed out in the first answer. It is acceptable to write multiple answers if they give different approaches to solving the same problem. But if you are pointing out different problems, that just shows further awareness of problems with the question. In particular, questions like this should be closed as "Needs more Focus". Keep in mind that Stack Overflow does not provide a help desk, and questions posted here are not support tickets to get someone else's code project to work. If there are multiple things wrong in the original code base, it is the OP's responsibility before posting to a) realize this; b) choose one specific thing to ask about; c) provide an MCVE for "what's wrong" questions (or a proper specification for "how do I" questions).
This information is important for other readers with the same symptoms. They should not be lead to believe that this is the solution to their symptoms.
If a question is supposed to be about why those symptoms come up in a specific situation, then it does not matter that the same symptoms can also come up in a different situation.
People who only know the symptoms they encountered and have no idea about how to debug the problem, cannot benefit from someone else's "what is wrong here?" question. They need a separate "what do these symptoms indicate?" question, which may or may not be feasible for the format. (If there are fundamentally too many ways, that are too different from each other, to cause the same symptoms, then the approach won't work. I've tried it before.)
If you really want to be helpful, self-answer your own question about the error. Frame it as a how-to instead of a "debugging" question. Maybe it could be something like "What do I need to do, to ensure that Cucumber can find and run my tests?". Maybe it could link to existing questions about specific things that went wrong / were not done (properly) in other cases.
Can anyone explain why this information is removed?
Because "meta" content of this sort is unacceptable in answers, full stop. Answers are supposed to answer the question, no more, no less. If that isn't possible, then don't try - and especially don't use the answer section to write something that doesn't qualify.
On the question I see that there is a dispute, and that it is being resolved, but what that dispute is, or how it is being resolved is unclear. As a party to the dispute, it seems weird that I'm not involved in it's resolution.
This is boilerplate text when posts are locked. The post is locked to avoid a rollback war - as is standard practice when a moderator gets involved. The "dispute" is implicitly about whether the answer should contain the content that was removed from your answer, and the current "resolution" is that it shall not.
There was initially a shorter lock, and promptly after that expired, you edited the post again to repeat the meta complaint (rephrased, but still fundamentally the same issue).
How do I appeal decisions by a moderator? Or get clarification? How does this even work?
By posting here. You should have done this before re-editing the answer, ignoring the point of the original lock.
Keep in mind that appeals usually don't go well because:
Moderators here generally know what they're doing;
There is a ton of sympathy for moderators on Stack Overflow because they are almost literally one-in-a-million users;
Generally the policy is pretty straightforward and you are expected (especially as an established user with an account over 9 years old) to understand fundamentals like this;
Complaints related to rollback wars especially don't usually go well for the author, because the site is supposed to be a collaborative project (your license of the content to the community includes the ability to make modifications, for a reason).
