Add a script implementing our standard "git gerrit-push" alias.  When
invoked, first check that the current branch is a named topic.  Then
fetch 'master' from the 'gerrit' remote repository so the local
repository can compute a minimal pack to push.  Finally, push the topic
to the 'gerrit' remote as "refs/for/master/$topic".

Add a .gitattributes line to match both "config.sample" and any config
file added by the containing project.

Configure a separate pushurl only if it is different from the main url.

Honor the $username placeholder in the 'gerrit.url' configuration value.
Configure a separate pushurl only if it is different from the main url.

When the topic stage has already been configured present the current
configuration and prompt for optional reconfiguration.  While at it,
make the topic stage remote name configurable by the project.

Add the "export-ignore" attribute to all such files.  Remove the
suggestion from the README since this should not be a responsibility
of the including project.

Interactively prompt the user for ~/.ssh/config setup.

Interactively prompt the user with Gerrit setup instructions.

Fetch the hooks right out of the local clone if possible.  Otherwise
fall back to a project-configured remote repository.

Prompt the user to configure user.name and user.email interactively.