Area import column header refinements

[anthonymarkQA]

Describe the bug 3 issues to resolve: Can be replicated in QA SPMIS instance: https://qa-sp-mis.newlogic.net/web/login

1. When importing area in area import. the value for the column headers must be Upper case, otherwise it will not be acknowledged by import feature. for ex: ADM0_en will not be recognized as it is not equal to ADM0_EN Therefore import feature should be case-insensitive to allow ADM0_en to be recognized.

2. Sometimes other spreadsheet software adds a trailing white space in the cell if you copy and paste value into the cell., (specifically libre office). This trailing white space leads to values not being read or accepted by import feature. Therefore, import feature should sanitize the values and remove trailing white spaces and then validate.

3. Digits for area codes are converted to decimal . should not convert to decimal and must be stored as whole number upon upload.

To Reproduce 1st issue:

1. Login to qa spmis as admin
2. Go to area>click on "areas" in the odoo header> click on area import
3. upload this file: use this (1).xlsx
4. Notice an odoo error will appear upon upload due to unrecognized "en" in "ADM0_en"

2nd issue:

1. Login to qa spmis as admin
2. Go to area>click on "areas" in the odoo header> click on area import
3. upload this file: use this (1).xlsx
4. notice an oddo error will appear upon upload due to trailing white space in "ADM0_PCODE "

3rd issue:

1. Login to qa spmis as admin
2. Go to area>click on "areas" in the odoo header> click on area import
3. upload this file: use this (1).xlsx
4. Notice upon successful upload, the area codes are converted to decimals 1.0 instead of 1.

Expected behavior All three issues stated are resolved. Screenshots

Additional context

🔔 Note: This ticket should address common considerations without including country-specific content. Please ensure all references are generic and applicable across various contexts.