Reduce unnecessary runner logs in gitea

[yp05327]

Feature Description

There are too many same FetchTask POST request logs in gitea which is unnecessary I think.
Maybe we can add a setting in app.ini to cut off these logs which have no errors.

For example:
logs, in #23636

Screenshots

No response

[wolfogre]

Actually, the logs are printed by routers logs, and the runners have to send requests to Gitea periodically.

Every HTTP request will cause a log line, even requests for js/css:

You could disable routers logs or config it to file, like:

[log]
MODE = console
;DISABLE_ROUTER_LOG=false
ROUTER = file

[wolfogre]

Reopen because maybe we can provide a filter for routers logs(or Gitea already has? I am not sure)

[yp05327]

IMO router logs are important in sometimes, but the request logs with no errors from runner, and repeat too many times like calling FetchTask, are not so important to be logged.
I don’t think simply disable router logs is a good answer for this problem. I agree to provide a router log filter to fix it.

[wxiaoguang]

Or rewrite the FetchTask to WebSocket, etc

[lunny]

Or rewrite the FetchTask to WebSocket, etc

It comes from WebSocket ...

[wxiaoguang]

Use WebSocket as a one-time short connection?

[lafriks]

Would be nice to classify what to log (UI, static resources, API, actions, internal API)