[Feature Request]: new release cycle and versioning

[tuxcanfly]

Implementation ideas

celestia-da versions were initially based on celestia-node and tightly coupled to it's releases.

As we have more breaking changes, this will be difficult to maintain. As such, starting from the next minor bump i.e. v0.13.x we should maintain celestia-da version independently from celestia-node version.

As we'll have different versions for celestia-da and celestia-node, there should be a version command that should output both versions.