Feature: Withdraw charges

[Aunshon]

All Submissions:

• My code follow the WordPress' coding standards
• My code satisfies feature requirements
• My code is tested
• My code passes the PHPCS tests
• My code has proper inline documentation
• I've included developer documentation (optional)
• I've added proper labels to this pull request

Changes proposed in this Pull Request:

New feature withdraw charge.

• Closes https://github.com/weDevsOfficial/dokan-pro/issues/2481

• Dokan Pro PR: https://github.com/getdokan/dokan-pro/pull/2692

Video Links: Introduction, Feature video

How to test the changes in this Pull Request:

1. First do not set charge and try to make a withdraw request. the experience will be as before.
2. Set withdraw charges and try to make request.
3. Check all the amount are alright as expected when applied charge.

Changelog entry

Admin can set a withdrawal charge (flat rate and percentage) for vendors so that admin can charge vendors for withdrawals based on the payment gateway and it will also reflect in the details report. Vendor can see how many charge will apply when request withdraw and show the charge and receivable amount in vendor dashboard list.

PR Self Review Checklist:

• Code is not following code style guidelines
• Bad naming: make sure you would understand your code if you read it a few months from now.
• KISS: Keep it simple, Sweetie (not stupid!).
• DRY: Don't Repeat Yourself.
• Code that is not readable: too many nested 'if's are a bad sign.
• Performance issues
• Complicated constructions that need refactoring or comments: code should almost always be self-explanatory.
• Grammar errors.

FOR PR REVIEWER ONLY:

As a reviewer, your feedback should be focused on the idea, not the person. Seek to understand, be respectful, and focus on constructive dialog.

As a contributor, your responsibility is to learn from suggestions and iterate your pull request should it be needed based on feedback. Seek to collaborate and produce the best possible contribution to the greater whole.

• Correct — Does the change do what it’s supposed to? ie: code 100% fulfilling the requirements?
• Secure — Would a nefarious party find some way to exploit this change? ie: everything is sanitized/escaped appropriately for any SQL or XSS injection possibilities?
• Readable — Will your future self be able to understand this change months down the road?
• Elegant — Does the change fit aesthetically within the overall style and architecture?

[Aunshon]

1. • Move withdraw charge from pro to lite.
2. • Combine the withdraw method section and withdraw charge section setting and make them one component
3. • Move upgrader from pro to lite
4. • Remove get charge api and do the task calculation to lite existing ajax