This was a 2 part issue requiring a JAMF Connect Configuration change as we had 2 options set to true that JAMF documentation said this would cause an issue.
NOTE: The use of user generic. Change it to the actual user account name. Should be first.last only, the @district145 is not needed.
These next 2 can be run remotely either via Apple Remote Desktop or terminal using ssh into the user's MacBook
dscl . -read /Users/user | grep -a1 failedLoginCount <---- Replace user with their first.last name. This will display the number of failed logins and if it's higher than 5 proceed
/usr/bin/pwpolicy -u user -authentication-allowed. <--------Replace user with their first.last name. Not completely sure what this does but it was part of the solution that worked
This must be run locally on the users MacBook in terminal, you can login use the wav admin user.
/usr/bin/pwpolicy -a wav -u user -setpassword <------again replace the user word with the actual user as in first.last and it's very important for the user to enter their known Google password as it will accept anything and the Google login will fail if the input the wrong Google password.
Confirmed by successfully logging into user's account from the Login Window and their current failedLoginCount is back to 0.
Still a work in progress but does resolve the issue.