DEVPROD-9149 Create manifest in periodic build job

[ZackarySantana]

DEVPROD-9149

Description

A user was reporting an old module revision being used rather than the latest. This is because we don't insert a manifest during our periodic build job and the base commit's manifest is used instead. This inserts a manifest for the periodic build job.

Testing

I simulated the situation with the commit queue repository and github merge queue repository (which I'll reference as CQ and GM respectively).

1. For the CQ repo, I added GM as a module (via a commit).
2. I added a periodic build in CQ.
3. I did a fresh commit in GM which is propagated in a log line in a CQ task (which will is now newer than the latest CQ commit).
4. It ran this version which has the older log line here.
5. I deployed this PR and it ran this version which has the new log line here. You can see the difference in log lines and the difference in the version manifest on the version page.

This is for the version without the update that does not create a manifest and uses the base commit (step 4):

This is for the version with the update that does create a manifest (step 5):

Documentation

TBA