Update everest-framework dependency to 0.13.0, bump version to 2024.4.0

[hikinggrass]

Describe your changes

Issue ticket number and link

Checklist before requesting a review

• I have performed a self-review of my code
• I have made corresponding changes to the documentation
• I read the contribution documentation and made sure that my changes meet its requirements

[hikinggrass]

@golovasteek @dorezyuk @SirVer I ran
bazelisk run update //...
after updating the dependencies.yaml, which worked without any issues in #631 but now it seems to be failing, how do you properly update these dependencies for bazel?

[SirVer]

mmh, the error is

Error in fail: error running 'git reset --hard v0.13.0' while working with @everest-framework:
fatal: ambiguous argument 'v0.13.0': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:

Which I do not understand, since the tag is clearly there. I ask @golovasteek to have a look at this, feel free to merge and we'll fix it in main or give us a day to look into it, your call @hikinggrass .

[golovasteek]

@golovasteek @dorezyuk @SirVer I ran bazelisk run update //... after updating the dependencies.yaml, which worked without any issues in #631 but now it seems to be failing, how do you properly update these dependencies for bazel?

The issue is that bazel is strict with using tags or commits, we can not just swap the value. We need to tell if it is tag or commit.

I've changed framework dependency from commit to tag here: #653

I'll think about how to make it more generic (it should be somehow done automatically by bazel run //:update)