feat: add fetch prune & delete command

[devjiwonchoi]

This PR is port of closed PR #183955

Resolves #183906

[devjiwonchoi]

Hey everyone, I’m going to take a look at this PR within a month and add tests and refactor if eligible. Afterwards I’ll try to contact maintainers for review. Thank you for your patience.

[devjiwonchoi]

@lszomoru Sorry to ping you, but respectfully requesting a review. So that you know, this PR and issue #183906 have a sum of 60+ upvotes.

[devjiwonchoi]

Suggested change

	// TODO: origin is hardcoded
	.map((el) => el.match(branchRegex)?.[1]?.replace('origin/', '') ?? '')
	.map((el) => el.match(branchRegex)?.[1]?.replace('origin/', '') ?? '')

I don't think there will be edge cases for remote origin, or?

[prhasn]

LGTM

[devjiwonchoi]

Hi @lszomoru, I hope you're doing well! I wanted to check in regarding a PR that's been waiting for your review for a year now. Could you let me know if you're able to take a look in the near future?

[devjiwonchoi]

@bpasero

Hi, sorry to ping you as this PR been getting much attention from the community, but unfortunately, it hasn't received any feedback for a year now.

I've opened this PR encouraged by #183906 (comment), hope this PR gets any feedback from the team.

[jimmyn]

I am using npx git-removed-branches --prune as an alternative until this feature is implemented.