feat: [Commands] lang:find show bad keys when scanning

[neznaika0]

Description
I tried to add a list of bad keys when scanning.
Now this is not exactly what @kenjis was talking about, but it's still better than nothing
Example:

$ ./spark lang:find --dir Controllers/Translation --verbose

CodeIgniter v4.4.3 Command Line Tool - Server Time: 2023-11-04 08:23:17 UTC+00:00

File found: Controllers/Translation/TranslationNested/TranslationFour.php
File found: Controllers/Translation/TranslationOne.php
File found: Controllers/Translation/TranslationThree.php
File found: Controllers/Translation/TranslationTwo.php
Files found: 4
New translates found: 0
Bad translates found: 5
+---+------------------------+
| № | Bad key                |
+---+------------------------+
| 0 | TranslationTwo         |
| 1 | .invalid_key           |
| 2 | TranslationTwo.        |
| 3 | TranslationTwo...      |
| 4 | ..invalid_nested_key.. |
+---+------------------------+

All operations done!

---

Originally posted by @kenjis in #7896 (comment)

I say on removing lang() from the code, or changing the argument.
E.g. lang('Cache.unabelToWrite') → lang('Cache.unableToWrite')
Cache.unabelToWrite is gone (but not deleted in the lang file), and Cache.unableToWrite is added.

I want to say, if there are items in the lang files that are not used by lang(),
it seems better to have a way to know them.

Checklist:

• Securely signed commits
• Component(s) with PHPDoc blocks, only if necessary or adds value
• Unit testing, with >80% coverage
• User guide updated
• Conforms to style guide

[kenjis]

What do you need the No. for? I want the file paths.

Suggested change

	CLI::table($tableBadRows, ['№', 'Bad key']);
	CLI::table($tableBadRows, ['№', 'Bad Key']);

[neznaika0]

The number is just for understanding which line. I think file paths are not an option to show. Since one language key can be in ~1000 different files. How do you see it?

[kenjis]

If a bad key is used in 1000 files, then those 1000 locations should be shown.

No.	Bad Key	File
1	BadKey1	path/to/file1.php
2	BadKey1	path/to/file2.php
...	...	...
1000	BadKey1	path/to/file1000.php

[neznaika0]

Heh, I'll try to do it.

[kenjis]

The variable names are difficult to understand. Don't use [0] or [1].
Name meaningful variable names.

[neznaika0]

Good. this is because the function returns multiple values instead of one

[neznaika0]

Do you have a suggestion on how to check existing translations from app/Language/? Should there be a separate lang command:validate, because the current code will be too large if you create the --validate flag?

[kenjis]

@neznaika0 You can create any classes for the commend.
See https://github.com/codeigniter4/CodeIgniter4/tree/develop/system/Commands/Utilities/Routes