Sync project branch improvements

The repository appears to be initially created as a shallow clone.
We need both branches in order to merge between two branches.  Fetch the
remote repository with the unshallow option.  If that command fails,
then fetch the remote repository without the unshallow option.  The hope
is that one of the two fetch commands will succeed.

Configure the user email address and user name in the repository so
that the merge does not fail with the message that user name and user
email are not configured.  The email address is fake, since no email is
accepted at the jenkins.io site.

Perform the merge with the `--no-edit` command so that merge knows it
should not open an editor.  May be unnecessary, but should not be harmful.

Author: MarkEWaite

.github/workflows/sync-project-branch.yml

@@ -12,8 +12,10 @@ jobs:
         with:
           ref: gsoc-2023-project
       - run: |
-          git fetch --unshallow origin
-          git merge origin/master
+          git fetch --unshallow origin || git fetch origin
+          git config user.email "sync-project-branch@jenkins.io"
+          git config user.name "Sync project branch action"
+          git merge --no-edit origin/master
       - uses: peter-evans/create-pull-request@v5
         with:
           title: Merge remote-tracking branch `origin/master` into `gsoc-2023-project`