ENH: allow user to infer SAS file encoding; add correct encoding names
- [x] closes #48048 (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.
I have included release information; this would fit into an enhancement section, right?

Additionally: If you think that this issue/PR is worthwile, I'd include all the other [encoding options from the SAS documentation](https://support.sas.com/documentation/onlinedoc/dfdmstudio/2.6/dmpdmsug/Content/dfU_Encodings_SAS.html) as well to be complete with all use cases. > Additionally: If you think that this issue/PR is worthwile, I'd include all the other [encoding options from the SAS documentation](https://support.sas.com/documentation/onlinedoc/dfdmstudio/2.6/dmpdmsug/Content/dfU_Encodings_SAS.html) as well to be complete with all use cases.

I have now included the other encoding names, though I don't know how to _factually_ test them; I just know that using these within Python's `encode(...)` does not throw an error :) @mroeschke Is this done in your opinion? :-) The `Data Manager` check seems to have failed for unrelated reasons; do you mind restarting? > @mroeschke Is this done in your opinion? :-) The `Data Manager` check seems to have failed for unrelated reasons; do you mind restarting?

Would you mind merging in main and moving the release note to `1.6.0.rst`? We are cutting a 1.5.0 fairly soon so we are freezing changes like these into the 1.5 release Does this not make the 1.5 release because of the SAS7BDAT reader refactoring here (#47403)  (and others)?

But of course, will do once the 1.6.0 doc is merged / started (#48221) > Does this not make the 1.5 release because of the SAS7BDAT reader refactoring here (#47403) (and others)?
> 
> But of course, will do once the 1.6.0 doc is merged / started (#48221)

The team is releasing the 1.5rc in the next few days so we want to make minimal changes. It may have a change to make it though depending if other team members find it appropriate.  Have rebased (and uncluttered the PR from the other commits) and moved into the `1.6.0` release notes. ✅ 
 Sorry for the delay here. Just needs to resolve the merge conflict otherwise LGTM @mroeschke It has been done! Thanks @YYYasin19! 