Repository: litestar-org/litestar

Issue:
Bug: New `create_static_files_router` automatically adds routes to schema docs
### Description

I found this suprising when using the new static files feature that
1: It auto adds these to the schema
2: It adds them under a sort've "ugly" router header `default`

We should fix one or both of those


### URL to code causing the issue

_No response_

### MCVE

```python
from litestar import Litestar
from litestar.static_files import create_static_files_router

app = Litestar(
    route_handlers=[
        create_static_files_router(directories=["assets"], path="/static"),
    ],
)
```


### Steps to reproduce

```bash
1. run mcve
2. visit /schema
3. See schema for default
```


### Screenshots
<img width="508" alt="image" src="https://github.com/litestar-org/litestar/assets/45884264/a6145e1a-370f-4105-bfec-cf73bddc90cd">

### Logs

_No response_

### Litestar Version

2.7/2.8

### Platform

- [X] Linux
- [X] Mac
- [X] Windows
- [ ] Other (Please specify in the description above)


Discussion:
Why wouldn't it add them to the schema? It's just regular route handlers, which, by default, are added to the schema. You can use the regular `include_in_schema=False` if you don't want them included.

Not sure about the name; We do include a `name` param which defaults to `static`. No idea where the `default` comes from, that might be a bug. 
We didn't include them before, but I feel like - by default - they should be disabled. 
The `default` is a tagless section iirc.

I'm fine with whatever here, but at the very least I hope we would tag this as something more not-`default`-ey
> The `default` is a tagless section iirc.

If you pass `tags=["static"]` (or whatever you want to call it) to the `create_static_files_router()` function, does that replace the "default" section? Maybe we should have a default that is not `None` for that?
I, for one, chose to stick with StaticFilesConfig as much as possible just because it does NOT add the routes to the schema docs. Since I'll never use them, I'd rather not see/have them there. So, for what it's worth, I'd also classify this as a bug (especially if you take into consideration that create_static_files_router is presented as the replacement for StaticFilesConfig, but it does not replace/mimic its behavior exactly).

Resolving patch:
diff --git a/litestar/static_files/config.py b/litestar/static_files/config.py
--- a/litestar/static_files/config.py
+++ b/litestar/static_files/config.py
@@ -10,7 +10,6 @@
 from litestar.response.file import ASGIFileResponse  # noqa: TCH001
 from litestar.router import Router
 from litestar.static_files.base import StaticFiles
-from litestar.types import Empty
 from litestar.utils import normalize_path, warn_deprecation
 
 __all__ = ("StaticFilesConfig",)
@@ -119,7 +118,7 @@ def create_static_files_router(
     cache_control: CacheControlHeader | None = None,
     exception_handlers: ExceptionHandlersMap | None = None,
     guards: list[Guard] | None = None,
-    include_in_schema: bool | EmptyType = Empty,
+    include_in_schema: bool | EmptyType = False,
     middleware: Sequence[Middleware] | None = None,
     opt: dict[str, Any] | None = None,
     security: Sequence[SecurityRequirement] | None = None,


Test patch: