[Documentation]: The docs don't always prepend the package to types

Proposal

In the docs, many pages have code example you can copy, but those examples don't always contain the package that contains the structs used in the example as a prefix, this is the case for the Dockerfile docs, parts of the networking docs, and the files and mounts docs, to name a few.

This makes this code not directly usable when a user wants to try things out by first copy/pasting the example, then modifying once they see what happens. It's a minor thing, but testcontainers. needs to be prefixed to every struct every time they copy something, which can lead to errors if they forget to do so.

It'd be great if the docs could include these prefix on all structs, or possibly have the examples in context as a separate tab in the code blocks, so we can see the code used in a real test.

Start with the code examples in the Dockerfile, networking, and files and mounts documentation pages linked in the issue. Check each copied example for structs that lack the testcontainers package prefix, then verify that the examples are directly usable without adding missing prefixes; consider whether an in-context example tab is needed if simple prefixing is insufficient.