sparse: don't enable on clone if it was a narrow clone

Authored by pulkit.

Description

sparse: don't enable on clone if it was a narrow clone

When both sparse and narrow extensions are enabled and we do a narrow clone,
sparse enables itself because it reads --include flag and thinks that user is
trying to do a sparse clone.

This patch changes that behavior, and now if both extensions are enabled and
user passes --narrow, then the includes and excludes won't be considered as
part of sparse profile.

Differential Revision: https://phab.mercurial-scm.org/D5479