🔎 feat: Admin dashboard withdraw advanced filtering with log exporting

[devAsadNur]

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:

• Closes Need a withdraw and log sorting option along with admin to view vendor statement with pdf generation for printing #324.

How to test the changes in this Pull Request:

Changelog entry

feat: Admin dashboard withdraws advanced filtering with CSV log exporting

Admin dashboard 'Withdraws' page has been integrated with some advanced filtering along with the log exporting feature. Now, admins can conveniently filter transactions based on the payment method and date range, enhancing their ability to analyze and manage withdrawals. Additionally, the feature to export CSV logs is also included, allowing for easy tracking and record-keeping. These integrations aim to empower the marketplace owner with comprehensive tools for efficient withdrawal management within the dashboard.

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?

[nurul-umbhiya]

kindly handle proper error handling for all API calls.
Example:

dokan.api.get('/withdraw/payment_methods')
            .done( ( response ) => {
                   this.paymentMethods = [ { id: '', text: '' } ].concat( response.map( payment_method => {
                        return {
                            id: payment_method.id,
                            text: payment_method.title
                        }
                    } ) );
                    jQuery( '#filter-payment-methods' ).select2( {
                        data: this.paymentMethods,
                    } ).val( this.filter.payment_method ).trigger( 'change' );
            }).always( () => {
                
            }).fail( ( jqXHR ) => {
                this.paymentMethods = [ { id: '', text: '' } ].
                let message = dokan_handle_ajax_error( jqXHR );
                if ( message ) {
                    self.showErrorAlert( message );
                }
            });