Fix esp32 IDF version number handling for patch releases

[mikee47]

Patch releases such as v5.0.5 break toolchain identification since we require just 'v5.0'.
This PR fixes that issue.

Note that all sming esp32 IDF versions have been brought up to date by merging latest release branch for each version.
Tags have have been applied as follows; the latest merged upstream commit is shown.

Sming branch	Tag	Espressif Tag	Date
sming/release/v4.3	v4.3.7-sming	v4.3.7-1-g3a71941503	2/1/2024
sming/release/v4.4	v4.4.6-sming	v4.4.6-374-gbb8dd9d35b	3/1/2024
sming/release/v5.0	v5.0.5-sming	v5.0.5-166-g209a0361c0	5/1/2024
sming/release/v5.2	v5.2-beta1-sming	v5.2-beta1-263-ge49823f10c	18/12/2023

[what-the-diff]

PR Summary

• Simplified Version Information
  The code has been altered to provide cleaner, more straightforward version information. The IDF_VERSION variable, which used to contain hyphen-separated numbers and additional details, is now simplified. It strictly represents major and minor version numbers, making it easier to identify the software's version at a glance. This change could simplify version tracking and compatibility checks in the future.

[mikee47]

@slaff I'm having second thoughts about doing this. The version numbers from git describe don't reflect merges, etc. I'm planning to use tags like v4.3.7-sming so this PR won't be needed.

[mikee47]

@slaff OK, we'll keep this PR but have restarted the esp32 CI checks to ensure the newly tagged IDF branches are handled correctly.

[slaff]

@mikee47 is this PR ready?

[mikee47]

@slaff Yes, all done.