I can identify a lot with what you said; one of my biggest weaknesses is being afraid to ask questions, fearing it might signal my lack of trying to figure things out on my own, and I can't seem to know when I'm actually wasting too much time not asking.

Personally, if I were to join a new team in the future, I'd first ask what the preferred toolset to debug is, along with any shortcuts (bash commands, way of setting up terminals, any admin UIs) they use, because it can greatly tighten your feedback loop when you test code you write, or poke around, etc. Maybe even pair with one of them while they solve a not so trivial bug, asking them to voice out what questions they're asking in the their head, how they know which file to look for or what to global search for, and articulate how they traverse through their tree of knowledge.

I've seen interns that were energetic, enthusiastic, and really felt no shame or stupidity in asking questions, even more trivial ones, because they looked like they were genuinely curious. They soaked up knowledge like a sponge and it was evident that they had nothing to lose after months of relentless question-asking - and very fortunately my team's culture tolerated that. Your team should encourage and support curiosity, speaking the language of logic, reason, and hopefully even helping others somewhat selflessly.