fix(config): allow the user to disable default filters by setting the…

[Sam-programs]

I am not sure if this is the best way to allow the user to fix the issue.

Fixes #769.

[ilan-schemoul]

filter = { any = false } can be confusing. Why any = false would mean accept any ?

Other ideas :

• filter = "no_filter"
• filter = require("noice").no_filter"
• filter = "disabled"
• A new field no_filter so you can do no_filter = true

[Sam-programs]

I ended up using a clear_filters key to allow the user to clear the builtin filters, and optionally add their own filters in the same table.
e.g.:

  {
    clear_filters = true,
    event = "notify",
  }

[github-actions]

This PR is stale because it has been open 60 days with no activity.

[ilan-schemoul]

@folke