Import/export app: add sample column mapping wizard fixture

[sridharkalaibala]

Parent: #34

Problem

CSV import/export is a useful Community Edition app, but column mapping needs fake examples that contributors can test.

Boundary

Do not import real merchant files or change database import behavior in this issue.

Acceptance criteria

• Add sample CSV files for products and customers with intentionally varied column names.
• Define expected mapping output.
• Include one invalid file with a clear expected error.
• Document how the fixture supports the local import/export app.

[Sj14122004]

Hi @sridharkalaibala, I’d like to work on this issue.

I’ll add the requested sample product and customer CSV fixtures with intentionally varied column names, define the expected column mappings, and include an invalid fixture with its expected error. I’ll also document how these fixtures can be used with the local Community Edition import/export app, without changing the existing database import behavior.

I’ll review the existing fixture/import-export structure first and then submit a PR referencing #161.

[sridharkalaibala]

Thanks, @Sj14122004. Assigned.

Please start with this issue first and keep only #161 active for now. One focused issue at a time is easier to review and gets merged faster.

Good starting points in the repo:

• existing sample files: frontend/static/Import_sample_files/
• existing import template coverage: tests/import-templates.test.js

For this PR, please keep the scope to sample fixtures and expected mapping documentation/test data: product CSV, customer CSV, one invalid CSV with the expected error, and a short note explaining how the local Community Edition import/export app should use them. Please do not change the existing database import behavior in this PR.