Add the daemon config UI

[egbicker]

Adds the user interface components for fapolicyd configuration editing and deployment.

Closes #830

[egbicker]

@jw3 I'm trying to implement the ConfigChangeset but even after rebuilding the rust layer I'm still getting AttributeError: module 'fapolicy_analyzer' has no attribute 'ConfigChangeset'

[jw3]

@jw3 I'm trying to implement the ConfigChangeset but even after rebuilding the rust layer I'm still getting AttributeError: module 'fapolicy_analyzer' has no attribute 'ConfigChangeset'

I missed a registration call in #908. #910 adds it and adds an example config changest usage.

[jw3]

✔️ Deployment nearly working, needs #911

---

There is also something going on that causes the unsaved rule changes dialog to always pop up, even when no rules have been edited.

[jw3]

@egbicker do you have tests coming for the new stuff?

[egbicker]

@jw3 Just got them pushed

[jw3]

Whats going on here?

[egbicker]

It's trying to load the changeset data and now we have 2 Changeset that return as string and the RuleChangeset has additional exceptions in the rust layer (I think its something about having 0 rules)

[jw3]

I was wondering about the nesting of the second try. Was that intended?

[egbicker]

It was but not like that. Good catch.

[jw3]

This is looking pretty good. A few things

• Noted the nested exception handling above for clarification
• I still saw the unsaved rule notification, but that looks like a problem with the rules view state management Text editor state issues #912
• Can a summary of config changes be added to this view? What bindings do we need added for this?
  

[jw3]

Added #912 describing some related concerns. Doesnt have to be fixed for this PR, but could be if simple enough.

Another thought with this is that the unsaved rule edit check would apply to config as well.

[egbicker]

@jw3 I believe we'd need a binding like rules_difference

[jw3]

#913 is on the way