Introduce CAPTCHA Requirements to the login pages

[SaadAli100]

PR Template

Any italic text should be deleted from the final Pull Request text, including this line

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes # (issue)

Type of change

Please delete options that are not relevant.

• Bug fix (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)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

Testing Checklist

• Tested in latest Chrome
• Tested in latest Safari
• Tested in latest Firefox

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have requested a review from NAMES HERE on the Pull Request

Notes for PRs

Below the commit message field you decide whether you are committing your changes to the current branch or a new branch. If the current brain is the main branch (develop), commit to a new branch.

Filling In CheckBox Example

• Example Filled
• Example Empty

[SaadAli100]

Register your website for reCAPTCHA by visiting the Google reCAPTCHA website. Decide whether to utilize reCAPTCHA v2 or v3, depending on your preference. You will receive a site key and a secret key upon registration/login.

add the reCAPTCHA widget to your form. Place this inside your registration/login form where you want the CAPTCHA to appear: data-sitekey="YOUR_SITE_KEY"

Verify the server-side reCAPTCHA response:
Google reCAPTCHA sends you a response once the form is submitted, which you should check on your server. Utilizing your secret key and response token, send a request to Google via your server-side script.

[hmm007]

This threw up an error (cos I didn't want to register a site key) but as long as Dolfin gets it own site key it will be fine.

I think better spacing would be best though - because it current blocks some text.

It has been noted it may be a screen size issue, because it was tested on a 22" screen by SaadAli10 - however, there should be some flexibility and adaptation to bigger or smaller screen sizes.