Fix --level not working with path argument

[veeceey]

Fixes #1701

When using --recurse --level=N with an explicit path argument (absolute or relative), the level limit was being ignored and only top-level contents were shown. This happened because the recursion depth was calculated from the total number of path components rather than tracking the relative depth from the starting directory.

For example, passing /Users/foo/bar/mydir would start the depth counter at 5+ (from path components), instantly exceeding any reasonable --level value. Meanwhile, running from the current directory (.) had only 1 component, so --level worked fine there.

The fix replaces the path-component-based depth calculation with a simple counter that starts at 0 and increments by 1 at each recursion level, making the behavior consistent regardless of how the path is specified.

Before:

$ eza --recurse --level=3 /tmp/test-dir
a.txt  foo  level1
# no subdirectories shown despite --level=3

After:

$ eza --recurse --level=3 /tmp/test-dir
a.txt  foo  level1

/tmp/test-dir/foo:
bar  readme.txt

/tmp/test-dir/foo/bar:
baz  test.txt

/tmp/test-dir/level1:
level2

/tmp/test-dir/level1/level2:
level3

Tested with absolute paths, relative paths, --tree --level, and --recurse without --level to confirm all cases work correctly. Added an integration test for --recurse --level with a path argument.

[veeceey]

giving this a little bump — let me know if it needs any work