A couple minor bugs with reporting in kapitan init

[dsansot-ru]

Describe the bug/feature
There are a couple of issues with the output of kapitan init:

1. It assumes the target directory was empty so shows all files in the target directory as being populated by init. I ran into this by running kapitan init in an empty git repo and was curious why kapitan was writing files to my .git directory.
2. It doesn't actually show all the files it did populate. I think this is an issue with the way it walks the tree.

To Reproduce
Steps to reproduce the behavior:

1. Run kapitan init

Expected behavior
Accurately log the files that were written.

Screenshots

On empty directory:

(venv) $ kapitan init --directory kapitan-init-test/
Populated kapitan-init-test/ with:
kapitan-init-test/
kapitan-init-test/inventory
kapitan-init-test/inventory/classes
	 common.yml
	 my_component.yml
kapitan-init-test/templates
kapitan-init-test/templates/scripts
	 my_script.sh
(venv) $ tree kapitan-init-test/
kapitan-init-test/
├── components
│   ├── my_component
│   │   └── my_component.jsonnet
│   └── other_component
│       ├── __init__.py
│       └── __pycache__
│           └── __init__.cpython-37.pyc
├── inventory
│   ├── classes
│   │   ├── common.yml
│   │   └── my_component.yml
│   └── targets
│       └── my_target.yml
└── templates
    ├── docs
    │   └── my_readme.md
    └── scripts
        └── my_script.sh

10 directories, 8 files

If it's a bug (please complete the following information):

• python --version:
  Python 3.7.2
• pip3 --version:
  pip 19.1.1
• Are you using pyenv or virtualenv?
python3 -m venv venv

[dsansot-ru]

BTW

$ kapitan --version
0.23.1