fix: create single leave ledger encashment entry for carry forwarding leave type (backport #2614)

[mergify]

Issue

Double ledger entry is created for encashment if leave type is carry forwarding, which doesn't expire normally through expire leave job, leading to extra leaves which could be incorrectly carry forwarded with new allocation

---

Before

After

Fix

Added a condition to check if leave type is carry forwarding before creating second leave ledger entry

---

This is an automatic backport of pull request #2614 done by Mergify.

[mergify]

Cherry-pick of d8e4234 has failed:

On branch mergify/bp/version-14-hotfix/pr-2614
Your branch is up to date with 'origin/version-14-hotfix'.

You are currently cherry-picking commit d8e42343.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   hrms/hr/doctype/leave_encashment/leave_encashment.py

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[frappe-pr-bot]

🎉 This PR is included in version 14.36.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀