I have a very different feeling about the OPs situation though. This is not about junior people asking too many questions or being lazy or incompetent, it is about a personality of people who are just entitled and demanding and just generally bitter assholes. Not typically seen in juniors!
The general consensus at these places was that getting to the information faster is preferable. We have a team chat channel for a reason, ask their. Don't stop your search, and don't ask first thing, but after a cursory glance, ask. Then continue to search on your own. If someone knows the answer and sees the question, they should respond. If you find the answer first, update the thread and answer your own question in case it helps anyone else.
That said, I agree if the answer was easily found in a google search. That's the kind of basic info an engineer/developer should be able to answer on their own with research and self-exploration.
It's key to be able to tell quickly whether the answer/info you're looking for is likely to be a common/general piece of info or a company/industry specific piece of knowledge that might not be found widely.
A junior dev may ask a lot of questions but that would be like, "Where is that documented? How do I read that? I don't understand what it's saying." A senior person might have already grokked a lot of it but didn't realize there was hidden context somewhere else, so when they say they couldn't find the documentation you show them and they go back to read it. A hostile student (someone who wants to be force-fed info instead of reading themselves) would pepper you with questions showing they didn't in good faith read any of the docs, but they wouldn't lie and say the docs weren't there. This is someone who thought that you were slacking off or wasting time and want to show that, and they'll keep at it until they can find something to stick. And if they can't, they'll make you have two mutually exclusive things to be true in order to satisfy them.