no longer use native rebase to find commits

seems pointless & hacky to launch 2 rebases instead of finding the
commits ourselves & then only launching the rebase when appropriate
to do the actual rebasing.
because of stuff like hooks etc., it just doesn't feel right.

i don't know if there's stuff we're missing out on that native rebase
is better at, esp. w/ edge cases, but i suppose we'll have to find out.

Signed-off-by: Kipras Melnikovas <kipras@kipras.org>

git-stacked-rebase.ts

@@ -258,18 +258,18 @@ export const gitStackedRebase = async (
 			initialBranch,
 			currentBranch,
 			// __default__pathToStackedRebaseTodoFile
-			pathToStackedRebaseTodoFile,
-			() =>
-				getWantedCommitsWithBranchBoundariesUsingNativeGitRebase({
-					gitCmd: options.gitCmd,
-					repo,
-					initialBranch,
-					currentBranch,
-					dotGitDirPath,
-					pathToRegularRebaseTodoFile,
-					pathToStackedRebaseTodoFile,
-					pathToRegularRebaseDirInsideDotGit,
-				})
+			pathToStackedRebaseTodoFile
+			// () =>
+			// 	getWantedCommitsWithBranchBoundariesUsingNativeGitRebase({
+			// 		gitCmd: options.gitCmd,
+			// 		repo,
+			// 		initialBranch,
+			// 		currentBranch,
+			// 		dotGitDirPath,
+			// 		pathToRegularRebaseTodoFile,
+			// 		pathToStackedRebaseTodoFile,
+			// 		pathToRegularRebaseDirInsideDotGit,
+			// 	})
 		);
 
 		if (!wasRegularRebaseInProgress || options.viewTodoOnly) {
@@ -979,6 +979,7 @@ async function getWantedCommitsWithBranchBoundariesOurCustomImpl(
 	return extendCommitsWithBranchEnds(repo, bb, wantedCommits);
 }
 
+noop(getWantedCommitsWithBranchBoundariesUsingNativeGitRebase);
 async function getWantedCommitsWithBranchBoundariesUsingNativeGitRebase({
 	gitCmd,
 	repo,