[FR] [DAC] Add exceptions list and action connector text to import-rules logging messages

[eric-forte-elastic]

Repository Feature

Detections-as-Code (DaC) - (primarily custom rule management)

Problem Description

Currently in the Kibana import-rules command the text output does not show information as to what exception lists and action connectors were also successfully (or unsuccessfully) uploaded. Export rules does provide this information and it would be nice.

This is coming from a community slack comment.

Details

detection-rules on  main [$!?] is  v0.1.0 via  v3.12.6 (test_venv) on  eric.forte took 3s 
❯ python -m detection_rules kibana --space prod import-rules -o -e -ac -d dac_test/rules
Loaded config file: /home/forteea1/Code/clean_mains/detection-rules/.detection-rules-cfg.json

█▀▀▄ ▄▄▄ ▄▄▄ ▄▄▄ ▄▄▄ ▄▄▄ ▄▄▄ ▄▄▄ ▄   ▄      █▀▀▄ ▄  ▄ ▄   ▄▄▄ ▄▄▄
█  █ █▄▄  █  █▄▄ █    █   █  █ █ █▀▄ █      █▄▄▀ █  █ █   █▄▄ █▄▄
█▄▄▀ █▄▄  █  █▄▄ █▄▄  █  ▄█▄ █▄█ █ ▀▄█      █ ▀▄ █▄▄█ █▄▄ █▄▄ ▄▄█

2 rule(s) successfully imported
 - 794d2fc0-ecd0-4963-99da-fd587666b80d
 - e8e3af2a-11b8-4ab7-9ca1-c6db621ea89d

detection-rules on  main [$!?] is  v0.1.0 via  v3.12.6 (test_venv) on  eric.forte took 6s 
❯ python -m detection_rules kibana --space prod export-rules -e -ac -d dac_test/rules/
Loaded config file: /home/forteea1/Code/clean_mains/detection-rules/.detection-rules-cfg.json

█▀▀▄ ▄▄▄ ▄▄▄ ▄▄▄ ▄▄▄ ▄▄▄ ▄▄▄ ▄▄▄ ▄   ▄      █▀▀▄ ▄  ▄ ▄   ▄▄▄ ▄▄▄
█  █ █▄▄  █  █▄▄ █    █   █  █ █ █▀▄ █      █▄▄▀ █  █ █   █▄▄ █▄▄
█▄▄▀ █▄▄  █  █▄▄ █▄▄  █  ▄█▄ █▄█ █ ▀▄█      █ ▀▄ █▄▄█ █▄▄ █▄▄ ▄▄█

4 results exported
2 rules converted
0 exceptions exported
1 action connectors exported
2 rules saved to dac_test/rules
0 exception lists saved to /home/forteea1/Code/clean_mains/detection-rules/dac_test/exceptions
1 action connectors saved to /home/forteea1/Code/clean_mains/detection-rules/dac_test/action_connectors

Desired Solution

Desired solution would be to include the text output similarly to the export-rules command.

Considered Alternatives

No response

Additional Context

No response