Allow module devs and users to ignore specific conflicts

[ruipin]

Right now, libWrapper only has global toggles to disable all notifications related to detected conflicts.

Sometimes, conflicts are expected and known by a module dev or the user, and they do not want to see the notifications for them. However, disabling the notifications runs the risk of the user not being told of new conflicts after e.g. updating various modules.

• [x] The backend needs to be updated to support ignoring specific conflicts.

• [x] There should still be a toggle in the "Conflicts" pane to show all conflicts detected, even those that were ignored. This would allow to debug issues where ignores are too broad.

• [x] There should be an API that allows module devs to choose conflicts that the user should not be notified of.

• [ ] There should be a new config pane that allows the user to choose specific notifications they do not want to see again.

[ruipin]

v1.7.1.0 implements the backend for this, as well as the libWrapper.ignore_conflicts API for module developers to use.

A UI to expose this functionality to users directly will need to be added at some point.