Update finish login example

[mitar]

I think it is important to note that credential.Authenticator.CloneWarning should be checked (or willfully ignored). And also credential should be stored, otherwise counter checking does not really work?

Is it safe to just overwrite the credential or are there values in registration credential which are missing from the logic credential object?

Is there anything else which should be validated in business logic and is missing from the example?

[james-d-elliott]

The only other potential check that may be missing is checking the Backup Eligible flag. This flag can never change per spec semantics. But yes this is a good spot and it was on my list of things to address specifically with a helper function or breaking change.

Regardless the doc adjustment is a welcome one. Let me know if you want me to just commit as is, or if you'd like to handle the BE check too. I'll have to double check the other elements of the examples as they have not been updated in a while.

[mitar]

I think BE checks should just be handled internally and error out in my opinion. So I think it is fine to merge as-is.