MAINT: be more specific with output

Summary

Prevent the message that records are being inserted or updated when they are not. Now, each cfood prints how many records are inserted or updated if and only if some are changed or inserted.

Test Environment

Run the crawler in some environment.

Check List for the Author

Please, prepare your MR for a review. Be sure to write a summary and a focus and create gitlab comments for the reviewer. They should guide the reviewer through the changes, explain your changes and also point out open questions. For further good practices have a look at our review guidelines

• All automated tests pass
• Reference related Issues
• Up-to-date CHANGELOG.md
• Annotations in code (Gitlab comments)
  • Intent of new code
  • Problems with old code
  • Why this implementation?

Check List for the Reviewer

• I understand the intent of this MR
• All automated tests pass
• Up-to-date CHANGELOG.md
• The test environment setup works and the intended behavior is reproducible in the test environment
• In-code documentation and comments are up-to-date.
• Check: Are there spezifications? Are they satisfied?

For further good practices have a look at our review guidelines.

src/doc/crawler.rst

@@ -88,9 +88,9 @@ Typically, an invocation looks like:
 
    python3 crawl.py /someplace/
 
-.. Note:: For trying this out with the above mentioned example crawler from the integration tests,
+.. Note:: For trying out the above mentioned example crawler from the integration tests,
           make sure that the ``extroot`` directory in the ``integrationtests`` folder is used as
-          CaosDB's extroot directory,and call the crawler with ``python3 crawl.py /``.
+          CaosDB's extroot directory, and call the crawler indirectly via ``./test.sh``.
 
 In this case ``/someplace/`` identifies the path to be crawled **within
 CaosDB's file system**. You can browse the CaosDB file system by