feat: Add Blog Post: DVLA @ AI Engineering Lab Hackathon

[piprees]

@Simon-Evs and I have reviewed the guidelines and this blog post has been reviewed by all those who have contributed quotes, stories, and media etc. All technical details pertain to the Hackathon or general AI initiatives, with nothing sensitive.

Let us know if we need to make any changes.

Other changes:

• Adjusted the img styles to make sure they don't stretch when we specify a height attribute which is essential for CLS.
• Tweaked the <figure> short code to meet accessibility guidance (avoiding duplicate alt+caption issue, missing alt issue).
• Added decoding="async" to stop images render blocking the page even with loading="lazy".

I will open a follow-up linting PR up to look at fixing the other files.

---

## Content Guidelines

### Content Guidelines - Security

Consider if the content of your post, including and images, has any security concerns:

- would the information be revealing to an attacker?
- is the content too revealing of backend processes?
- do we need to make make specific details public?

If you have any doubt please seek support from the cyber security team before publishing your content.

### Content Guidelines - Reputation

You must consider if the content of your post could cause damage to the reputation of the organisation. 

If you have any doubt please seek support from the communications team before publishing your content.

## Approval Process

All changes to content must be approved by at least one person from the engineering review control group. This takes the form of a Github pull request and is automatically enforced.

Formal approval within the wider organisation is not required by default but may be requested based on e.g. security or reputational concerns.