Added hungarian translations, and hungarian number formatters

[nkelemen18]

Here is a checklist you should tick through before submitting a pull request:

• Implementation is clean
• Code adheres to the existing coding standards; e.g. no curlies for one-line blocks, no redundant empty lines between methods or code blocks, spaces rather than tabs, etc.
• No Code Analysis warnings
• There is proper unit test coverage
• If the code is copied from StackOverflow (or a blog or OSS) full disclosure is included. That includes required license files and/or file headers explaining where the code came from with proper attribution
• There are very few or no comments (because comments shouldn't be needed if you write clean code)
• Xml documentation is added/updated for the addition/change
• Your PR is (re)based on top of the latest commits from the main branch (more info below)
• Link to the issue(s) you're fixing from your PR description. Use fixes #<the issue number>
• Readme is updated if you change an existing feature or add a new one
• Run either build.cmd or build.ps1 and ensure there are no test failures

[SimonCropp]

can you explain this change. egy év seems correct

[nkelemen18]

Hello,

This is because I have addedd the missing hungarian translations to the resource file. egy év is correct, when toWords is set to true, othervise the number will be number, not word (1 vs egy).

I created new test cases to verify the word representation of TimeSpans.

https://github.com/Humanizr/Humanizer/pull/1501/files#diff-6829957358e12fc8868dd8833601a3630bc4d27a0489053daa4d863c2459dc7dR612

[SimonCropp]

@nkelemen18 thanks

@clairernovotny can you deploy a new beta