text: Title: logging of passing checks
  Body:         I would add something else on my side. It would be wonderful to have logged the passes as well (optionally ofc) 
  Here is a sample output:
  ```
  test_sandbox.py::TestSandbox::test_case1 
  ------------------------------- live log setup --------------------------------
  13:17:04.319 [INFO] INIT
  -------------------------------- live log call --------------------------------
  13:17:04.320 [FAIL] check 2 == 1 FAIL1
  13:17:04.853 [PASS] check 1 == 1 PASS
  13:17:04.854 [FAIL] check 0 == 1 FAIL2
  FAILED                                                                   [100%]
  testsuites\sandbox_test\test_sandbox.py:42 (TestSandbox.test_case1)
  FAILURE: check 2 == 1: FAIL1
  test_sandbox.py:44 in test_case1() -> self.steps.step_check()
  scripts\steps.py:25 in step_check() -> check.equal(2, 1, "FAIL1")
  
  FAILURE: check 0 == 1: FAIL2
  test_sandbox.py:44 in test_case1() -> self.steps.step_check()
  scripts\steps.py:27 in step_check() -> check.equal(0, 1, "FAIL2")
  
  ------------------------------------------------------------
  Failed Checks: 2
  ```
  
  What I did, I added two logging levels (PASS and FAIL) and just log them with message. 
  I think adding different log levels should not be a problem. I can create them on root logger in my project, and just specify them from command line as you suggest
  
  Why I even need a pass in test case?
  Well, I am using pytest for functional tests in my project, after execution I need to create a report what was tested. Having this in log will simplify the process
  
  @okken, does it make sense ?
  
  _Originally posted by @kapis90 in https://github.com/okken/pytest-check/issues/52#issuecomment-1377184662_
        