manifest: Matter applications versioning by VERSION file implemented

[LipinskiPNordicSemi]

This commit introduces VERSION file to unify versioning

test_chip: PR-648

[NordicBuilder]

The following west manifest projects have been modified in this Pull Request:

Name	Old Revision	New Revision	Diff
matter	nrfconnect/sdk-connectedhomeip@e54423d (master)	nrfconnect/sdk-connectedhomeip#370	nrfconnect/sdk-connectedhomeip#370/files

Note: This message is automatically posted and updated by the Manifest GitHub Action.

[NordicBuilder]

Test specification

CI/Jenkins/NRF

• Integration Platforms

CI/Jenkins/integration

Test Module	File based changes	Manually selected	West overwrite
test-fw-nrfconnect-chip	X

Detailed information of selected test modules

Note: This message is automatically posted and updated by the CI

[NordicBuilder]

You can find the documentation preview for this PR at this link. It will be updated about 10 minutes after the documentation build succeeds.

Note: This comment is automatically posted by the Documentation Publishing GitHub Action.

[kkasperczyk-no]

I would expect in this PR we should:

• align all samples and applications to start using VERSION (if this is what we want to start recommending)
• update documentation to describe both available solutions (Kconfig based and VERSION file based)
• update release notes

[kkasperczyk-no]

How about adding VERSION files to Matter bridge and weather station applications?

[LuDuda]

I wonder if we need description of DFU. At this point user is familiar with DFU procedure from the previous documentation pages.

What about to change this entire paragraph to something like this:

Suggested change

	Device Firmware Update (DFU) is the procedure of upgrading the application firmware version on a device.
	For example, you can transfer the updated images to the device by:
	* Upgrade over Bluetooth® Low Energy (LE).
	* :ref:`Upgrade over Matter (Matter OTA)<ug_matter_overview_dfu>`, where the updates are sent over the Matter fabric.
	Before creating and performing DFU, you need to prepare a proper versioning configuration.
	Versioning can be maintained by creating a :ref:`VERSION<app-version-details>` file, or by using Kconfig options.
	To effectively deploy a Matter product, it is essential to implement application version management. This versioning is crucial for managing firmware upgrades on devices, and it is also displayed within ecosystem applications, as provided by the Basic Information cluster.
	There are two primary approaches for maintaining versioning. It's important to note that these approaches should not be used simultaneously:
	Utilizing a VERSION file, as detailed in the Zephyr Project documentation: [Zephyr Project Versioning](https://docs.zephyrproject.org/latest/build/version/index.html#). This method involves defining the version information in a specific file format.
	Implementing dedicated Kconfig configurations. This approach uses Kconfig system configurations to set and manage the versioning details.
	Choose the approach that best aligns with your project requirements and infrastructure.

[LuDuda]

One more comment.. Here i do see " . (dot) TWEAK" but in below examples, i do see "+" sign. Maybe all is fine, but it might be confusing.

[LipinskiPNordicSemi]

Good point, I didn't catch that