Include git-hook regeneration in restore documentation

[wranders]

This PR is to include the git-hook regeneration command to the restore section of the Backup and Restore guide.

When migrating to a different installation method (eg. binary -> Docker), there is currently no mention of needing to regenerate git-hooks, causing push actions to fail on the new installation.

[codecov-io]

Codecov Report

Merging #8181 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #8181      +/-   ##
==========================================
+ Coverage   41.83%   41.84%   +<.01%     
==========================================
  Files         482      482              
  Lines       64613    64613              
==========================================
+ Hits        27033    27035       +2     
+ Misses      34109    34107       -2     
  Partials     3471     3471

Impacted Files	Coverage Δ
modules/log/event.go	65.64% <0%> (+1.02%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7a8e299...e73268a. Read the comment docs.

[wranders]

Suggestions added.

Using may in the consequence language was to cover the possibility that paths could be valid in a migration, but there's no harm in running the command in that case.

[guillep2k]

Suggestions added.

Using may in the consequence language was to cover the possibility that paths could be valid in a migration, but there's no harm in running the command in that case.

Of course you're right, but in a migration guide I think it's better to play safe for the reasons you mention.