Simplify config documentation and clarify default iteration behavior

[Copilot]

The config documentation was verbose and obscured the key fact that commands iterate over all namespaces and kinds by default. Users needed explicit guidance on when filtering is necessary versus optional.

Changes

Documentation

• Reduced README config example from 25 lines to 9 lines showing minimal setup
• Added explicit statement: "By default, all commands iterate over all namespaces and all kinds"
• Removed duplicate configuration section
• Updated CLI examples to demonstrate both default (no filters) and filtered usage

Code cleanup

• Removed redundant is None checks in config normalization (already handled by _as_list())
• Simplified namespace iteration logic in analyze_entity_fields.py by removing unreachable branches
• Fixed unused imports and modernized type hints to PEP 604 syntax (str | None)

Tests

• Added test verifying empty config lists trigger "iterate all" behavior

Example

Before (confusing):

namespaces: [""]  # [""] means include default namespace and allow discovery of others
kinds: []         # Empty/omit means discover all kinds per namespace

After (clear):

# Omit to process all namespaces and kinds (default behavior)
namespaces: ["custom-ns"]  # List specific namespaces
kinds: ["MyKind"]          # List specific kinds

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Config simplification</issue_title>
<issue_description>- It should iterate over all namespaces and all entities by default

• Only in case specific, through config file or by argument to lsu it should focus on a specific namespace and/or specific kind to check
• Simplify config, dropping not used stuff
• Update README.md, simplyfing it and removing old/not updated content

Update tests, docs.

After that, run tests and ensure all commands are working without issues.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Config simplification #7

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.