add oem battery profile version.

KBA-191111223725
[Platform]:
SM6150, SM7150, SM7250, Any platforms use PMI632
[Issue Description]:
If ever use a mismatched temporary profile before receive the matched profile, it may lead to
unexpected inaccurate/nonlinear soc issue, even though you have replaced the correct one, issue
still remains.
[Solution]:
The reason of this issue is because of the saving of incorrect battery info in SDAM, Qcom battery
gauge save the calculated battery info(l(CR) ESR, Capacity...) into the SDAM of PMIC, when reload
a new battery profile, these info will not be cleared, in other words, device will use the incorrect
data to calculate the Soc even though you have loaded a correct matched profile.
To solve this issue, there're two options, one is to re-plug the battery, so that SDAM data will be
cleared. The other option is to merge below workaround, and add device tree property "qcom,
oem-batt-profile-ver" to identify profile change, then driver code will do SDAM clear.

Change-Id: Ic06efb1ca869d541e9c93ad1a79e12e1b9f140ea
Signed-off-by: xieqiong2 <xieqiong2@lenovo.com>
Reviewed-on: https://gerrit.mot.com/1732317
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Wei Xu <xuwei9@lenovo.com>
Reviewed-by: Xiangpo Zhao <zhaoxp3@motorola.com>
Submit-Approved: Jira Key

qcom/qg-batterydata-ATL-4V45_6000mah.dtsi

@@ -9,6 +9,7 @@ qcom,ATL466271_6000mAh {
 	qcom,battery-therm-kohm = <100>; /* on sub-board 100K */
 	qcom,battery-type = "S88731AA1-qrd-ATL-4V45-6000mah";
 	qcom,qg-batt-profile-ver = <100>;
+        qcom,oem-batt-profile-ver = <1>;
 
 	/*qcom,step-chg-ranges = <3500000  4000000  8000000
 				4000001  4200000  6000000