[parser] feat: add memory parser

[Moocharr]

What does this PR do?

add memory parser
issue -> #42

Add concise overview of what this PR aims to achieve or accomplish. Reference related GitHub issues and PRs that help with the review.

Checklist Before Starting

• Search for similar PRs. Paste at least one query link here: ...
• Format the PR title as [{modules}] {type}: {description} (This will be checked by the CI)
  • {modules} include pipeline, parser, visualizer, data, deployment, perf, algo, env, doc, cfg, ci, misc
  • If this PR involves multiple modules, separate them with , like [mstx, ci]
  • {type} is in feat, fix, refactor, chore, test
  • If this PR breaks any API (CLI arguments, config, function signature, etc.), add [BREAKING] to the beginning of the title.
  • Example: [BREAKING][mstx, torch_profile] feat: support timeline parsing

Test

For changes that can not be tested by CI (e.g., algorithm implementation, new model support), validate by experiment(s) and show results like training curve plots, evaluation results, etc.

API and Usage Example

Demonstrate how the API changes if any, and provide usage example(s) if possible.

# Add code snippet or script demonstrating how to use this

Design & Code Changes

Demonstrate the high-level design if this PR is complex, and list the specific changes.

Checklist Before Submitting

Important

Please check all the following items before requesting a review, otherwise the reviewer might deprioritize this PR for review.

• Read the Contribute Guide.
• Apply pre-commit checks: pre-commit install && pre-commit run --all-files --show-diff-on-failure --color=always
• Add / Update the documentation.
• Add unit or end-to-end test(s) to the CI workflow to cover all the code. If not feasible, explain why: ...

[gemini-code-assist]

Code Review

This pull request introduces a new MemoryClusterParser to extract memory allocation data from Ascend Profiler outputs, including a design document, ijson-based streaming parsing, and comprehensive tests. The reviewer identified several critical issues: a naming mismatch in the MemoryEventRow schema that would cause KeyErrors in the base parser, potential ValueErrors when parsing empty CSV fields, missing validation rules for new data types, and brittle directory sorting logic. Addressing these points will ensure the parser is robust and compatible with the existing framework.