Add New-Exception, and PassThru parameter to exception commands

[johlju]

Pull Request (PR) description

• Wiki source file HOME was modified to not link to README for help after
  command documentation now is in the wiki.
• New-Exception
  • New command that creates and returns an [System.Exception].
• New-ArgumentException
  • Now takes a parameter PassThru that returns the error record that was
    created (and does not throw).
  • Now has a command alias New-InvalidArgumentException and the command
    was renamed to match the exception name.
• New-InvalidOperationException
  • Now takes a parameter PassThru that returns the error record that was
    created (and does not throw) (issue #98).
• New-InvalidResultException
  • Now takes a parameter PassThru that returns the error record that was
    created (and does not throw).
• New-NotImplementedException
  • Now takes a parameter PassThru that returns the error record that was
• New-InvalidDataException
  • The parameter Message has a parameter alias ErrorMessage to make
    the command have the same parameter names as the other New-*Exception
    commands.
• New-ObjectNotFoundException
  • Updated typo in comment-based help.

This Pull Request (PR) fixes the following issues

• Fixes New-InvalidOperationException: Suggest adding a PassThru parameter #98

Task list

• Added an entry to the change log under the Unreleased section of the
  file CHANGELOG.md. Entry should say what was changed and how that
  affects users (if applicable), and reference the issue being resolved
  (if applicable).
• Documentation added/updated in README.md.
• Comment-based help added/updated for all new/changed functions.
• Localization strings added/updated in all localization files as appropriate.
• Examples appropriately added/updated.
• Unit tests added/updated. See DSC Community Testing Guidelines.
• Integration tests added/updated (where possible). See
  DSC Community Testing Guidelines.
• New/changed code adheres to DSC Community Style Guidelines.

---

This change is 

[johlju]

Reviewed 12 of 12 files at r1, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion

---

source/Public/New-ObjectNotFoundException.ps1 line 52 at r1 (raw file):

    if ($null -eq $ErrorRecord)
    {
        $exception = New-Object -TypeName 'System.Exception' `

We can use the New-Exception for this instead? Also for New-InvalidResultExceptionx.

[johlju]

Reviewed 2 of 2 files at r2, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @johlju)

[johlju]

Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @johlju)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (1ada77f) 91% compared to head (8495e30) 91%.

Additional details and impacted files

@@         Coverage Diff         @@
##           main   #115   +/-   ##
===================================
  Coverage    91%    91%           
===================================
  Files        37     38    +1     
  Lines       664    668    +4     
===================================
+ Hits        609    613    +4     
  Misses       55     55           

Files	Coverage Δ
source/Public/New-ArgumentException.ps1	100% <100%> (ø)
source/Public/New-Exception.ps1	100% <100%> (ø)
source/Public/New-InvalidDataException.ps1	100% <ø> (ø)
source/Public/New-InvalidOperationException.ps1	100% <100%> (ø)
source/Public/New-InvalidResultException.ps1	100% <100%> (ø)
source/Public/New-NotImplementedException.ps1	100% <100%> (ø)
source/Public/New-ObjectNotFoundException.ps1	100% <100%> (ø)