add alternative column names for automatic matching

[alex552]

Proposed changes

In the current way the automatic column matching, the csv header has to match the field name exactly, but sometimes the header might have similar or alternative names for columns, this PR adds the possibility to define alternative names the column might have and hopefully be able to automatically match all columns.

Types of changes

What types of changes does your code introduce to Filament Import? Put an x in the boxes that apply

• [ x] ✨ New feature (non-breaking change which adds functionality)
• [ ] 🛠️ Bug fix (non-breaking change which fixes an issue)
• [ ] ❌ Breaking change (fix or feature that would cause existing functionality to change)
• [ ] 🧹 Code refactor
• [ ] ✅ Build configuration change
• [ ] 📝 Documentation
• [ ] 🗑️ Chore

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• [x] I have read the CONTRIBUTING doc
• [ ] I have signed the CLA
• [x] Lint and unit tests pass locally with my changes
• [x] I have added tests that prove my fix is effective or that my feature works
• [ ] I have added necessary documentation (if appropriate)
• [ ] Any dependent changes have been merged and published in downstream modules

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

[gabrieljaime]

I will be glad to get this change.. I need it

[frankyso]

Thanks