Invisible namespace for other projects under specific folder name

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Describe the bug

I have a lib project X that contains a folder named `Requests` with a file that has a namespace `X.Api.Dtos.Requests`.

If I try to use classes from the `X.Api.Dtos.Requests` into my ASPNET project that has X as a reference, the project says the namespace cannot be resolved.


But if you rename the folder `Requests` into something else, like `Request` as an example, the ASPNET project see the `X.Api.Dtos.Requests` namespace.


### Expected Behavior

The name of a folder shouldn't affect the visibility of a namespace in a project

### Steps To Reproduce

- Create an ASPNET proj
- Create a lib project
- Add the reference of the lib project to the ASPNET one
- Follow the steps in the description

### Exceptions (if any)

_No response_

### .NET Version

net6.0

### Anything else?

_No response_