Add getLoggerByQuotation and deprecate getCurrentLogger

[TheAngryByrd]

Proposed Changes

Add getLoggerByQuotation and deprecate getCurrentLogger.

getCurrentLogger uses the StackFrame and skip to try to figure out where we are in our codebase, however it can give really inconsistent results and lead programmers astray, even thought it seems like the most obvious path.

To alleviate the need to handroll your own fully qualified namespace strings I've added getLoggerByQuotation which allows you to write code like

namespace Bar 

module Foo = 
  let rec logger = LogProvider.getLoggerByQuotation <@ logger @>

Which will create a logger with the Bar.Foo path.

Also adds getLoggerByFunc which is useful only within functions.

    let hello name  =
        let logger2 = LogProvider.getLoggerByFunc ()
        // Starts the log out as an Informational log
        logger2.info(...)

Will result in SomeLib.Say.hello. This cannot protect against inlining but this is no worse than the StackFrame method.

Types of changes

What types of changes does your code introduce to FsLibLog?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• Build and tests pass locally
• I have added tests that prove my fix is effective or that my feature works (if appropriate)
• I have added necessary documentation (if appropriate)

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...