New package: ledger-autosync-1.2.0

[nazaradeh]

Testing the changes

• I tested the changes in this PR: YES
• Tested by creating a test .ofx file and running the program with it.

New package

• This new package conforms to the package requirements: YES

Local build testing

• I built this PR locally for my native architecture, (x86_64)
• I built this PR locally for these architectures (if supported. mark crossbuilds):
  • aarch64-musl
  • armv7l

Notes

• Closes Ledger autosync #24756. @Vaelatern, the author of that PR, has requested I open up a new PR with my review, so please do not close this PR as a duplicate.
• @Vaelatern if you'd like me to put you down as the maintainer for these, let me know. Either way, seems like a stable program that hasn't had/needed an update in years.
• Other than this PR being for a newer version than the old PR, I also patched out
  argparse instead of doing a do_check workaround.

[Vaelatern]

Only adjustment is to split into 4 packages

[nazaradeh]

Only adjustment is to split into 4 packages

Meaning four different PRs? I would think because it's four separate templates that it counts as 4 packages. Looking at how other people do PRs with multiple packages, I don't know what's different. Let me know!

[Vaelatern]

One PR, one git branch, but 4 commits between master and new-package-ledger-autosync-1.2.0

[Vaelatern]

So fun fact you can "rewrite history" to do this, then force pushing to have the work on the branch. You don't even need your local and remote branches to have the same name, if you don't want to (or it's easier that way).

[nazaradeh]

Ahh gotcha, right yes once it gets merged in you just see the commits on main. Thanks! I'm used to perforce for work but not git outside of personal projects so still learning.

Should be good now, then, after CI passes.