New oscam versioning

OScam recently moved from version 1.20 (10+ years old) to version 1.30 after introducing Streamrelay + libdvbcsa. There is the revision (known from SVN, now used as a git tag) and the sha, which clearly identifies a code change in a git repository or worldwide.

Based on these numbers and with the experience that a "managed" version system is difficult to implement for everyone involved, the following system, based on calendar versioning, should now be introduced:

• the major version changes from 1.30 to version 2
• the minor version switches to the 2-digit year of the last code change
• the build version changes to the 2-digit month of the last code change
• The number known from SVN and now continued as a tag is used as a revision
• the sha is carried as unique identification

So 1.30-r11768@0cf87d1a will be changed to 2.24.04-11768

• in May 2024, if there are new commits in the master branch: 2.24.05-11772 (revision is an example)
• in November 2024, if there are new commits in the master branch: 2.24.11-11801 (revision is an example)
• in January 2025 if there are new commits in the master branch: 2.25.01-11809 (revision is an example)

This means that the version number shows the time from which the code changes in the present oscam binary originate.

The display in the WebIf and protocols should be as follows:

• WebIf Label (top center): 2.24.04-11768
• WebIf Footer (below): Version: 2.24.04-11768 Git: 0cf87d1a
• oscam.version: Version: 2.24.04-11768@0cf87d1a
• CCcam log: 2.24.04-11768
• xml, json, etc: 2.24.04-11768