Update mocks
What does this MR do?
Simply updates mocks in our repository :)
Why was this MR needed?
After mockery update some time ago, generated mocks have a different comment at top. This is not a problem at all, but when regenerating mocks with make mocks (which is the only method that we should use), all mocks are being update - also the ones not related to currently developed changes. This ends with a MRs that have some changes not related directly to their scope (e.g. !934 (merged) at this moment). And it requires manual selection when doing git add to not add not related mocks into the MR commits.
This MR updates all our mocks to the new format, so when working with mocks in different MRs we will (re)generate only the mocks that are related to the MR context
Are there points in the code the reviewer needs to double check?
Does this MR meet the acceptance criteria?
-
Documentation created/updated - Tests
-
Added for this feature/bug -
All builds are passing
-
-
Branch has no merge conflicts with master(if you do - rebase it please)