ENH: Adding engine_kwargs to Excel engines for issue #40274
- [X] closes #40274 (Replace xxxx with the GitHub issue number)
- [x] [Tests added and passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#writing-tests) if fixing a bug or adding a new feature
- [x] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).
- [x] Added [type annotations](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#type-hints) to new arguments/methods/functions.
- [x] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.

@rhshadrach Changes have been made! Please let me know if I have missed anything else!

Quick question. Once this PR is approved, could this also close out issue [43053](https://github.com/pandas-dev/pandas/issues/43053) @rhshadrach Wondering if I should submit a GH issue to implement the same feature for the `to_excel` method? > @rhshadrach Wondering if I should submit a GH issue to implement the same feature for the `to_excel` method?

Yea - I think that makes sense to do! @rmhowe425 Please be aware that each time you merge main into this branch, it kicks off all the tests (30+hours of compute). This should be done only when needed - for example:
 - if there are conflicts
 - if you're aware of a PR that has been merged to main that touches on similar parts of the code
 - right before we merge this branch into main (to make sure all the tests still pass)

I don't think it needs to be done daily, or even once every couple of days. @rhshadrach 
![image](https://user-images.githubusercontent.com/45905457/229359156-0d935b7c-5665-43d2-be15-740fd378a993.png)
For some reason it seems like the Code Checks test isn't liking my attempts to revert this change...looking at the failing test, it appears that the specific test that failed was: `sort whatsnew entries by issue number.`

The reason that I initially moved this line in the documentation was due to a merge conflict...I'm wondering if the line in question does in fact belong where I placed it? Fixed merge conflict @MarcoGorelli wow okay never mind. Not sure what I did wrong before....Thanks for pointing that mistake out to me! looks right now, nice :)  @rhshadrach Pinging on green!

 @MarcoGorelli Looks like we're good to go! I think we just need your sign off? Awesome! Thanks @rmhowe425  Thanks for all the help guys! Really appreciate it! hi team, pls what pandas version is this targeted for? I cant find it on pandas 2.0.3
 @samukweku 2.1.0, which I believe will be released later today. If you check the "Files Changed", you'll see an entry in whatsnew/v2.1.0