Live merge

[DIPAD-Fran-Bryden]

As a contributor

By submitting this PR I confirm I have read and understood the Github Standards document and understand the role I play in ensuring standards, security, and assurance at DfT.

As a PR reviewer

By accepting this PR I understand my responsibilities as described in the the Github standards document.

Proposed changes

Merged in all three feature branches to hopefully reunite the unit testing family

Please note I have not done end to end testing on these, please check that everything works, tests run, and documentation is regenerated.

Types of changes

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

• Bugfix (change which fixes an issue)
• New feature (change which adds functionality)
• Documentation Update (change to naming or other documentation)

Points I have checked in my code

Put an x in the boxes that apply. You can also fill these out after creating the PR.

• I have added unit tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• I have checked that my changes have not broken any other functionality
• I have linked to any issues this PR fixes

Points for review

Add checkboxes here for any specific aspects of your PR you would like to be checked in peer review. If you don't specify anything here, the reviewer will check:

• All of your unit tests pass
• Your code is clear and easy to understand
• You have documented any new features
• They can run the code you have written
• Your changes do not break any other functionality

Security considerations

Put an x in the boxes that apply. You should have considered all of these points before submitting a PR.

• My code does not contain any secrets such as passwords, API keys, etc
• I have not accidentally uploaded any data to Github
• My code does not include any personal information such as names or email addresses

Who is reviewing this PR?

@Mo-Dell

[Mo-Dell]

Have checked and it looks like the code works, besides the error in create_bq_table() function (which I think you mentioned was fixed in another PR).