Fix memory leak in profiles sample

[gary-sweet]

Description

The 'textures' vector wasn't being cleaned up, resulting in 32 blocks of device memory being left initialized.

General Checklist:

Please ensure the following points are checked:

• My code follows the coding style
• I have reviewed file licenses
• I have commented any added functions (in line with Doxygen)
• I have commented any code that could be hard to understand
• My changes do not add any new compiler warnings
• My changes do not add any new validation layer errors or warnings
• I have used existing framework/helper functions where possible
• My changes do not add any regressions
• I have tested every sample to ensure everything runs correctly
• This PR describes the scope and expected impact of the changes I am making

Note: The Samples CI runs a number of checks including:

• I have updated the header Copyright to reflect the current year (CI build will fail if Copyright is out of date)
• My changes build on Windows, Linux, macOS and Android. Otherwise I have documented any exceptions

If this PR contains framework changes:

• I did a full batch run using the batch command line argument to make sure all samples still work properly

[asuessenbach]

While you're fixing memory leaks...
Shouldn't the images, image_views, the sampler and the base_descriptor_set be destroyed/freed as well?

[gary-sweet]

While you're fixing memory leaks... Shouldn't the images, image_views, the sampler and the base_descriptor_set be destroyed/freed as well?

Well, my memory leak detector hasn't shown those up, so not in this PR at least.

[asuessenbach]

Indeed, there are no validation layer issues with the images and those other resources!
And an API Dump tells me, vkDestroyImage is called for those images.
But I don't get where.

[SaschaWillems]

The sample uses the profiles library for instance setup, so no validation here. I'll look into it.

The PR itself LGTM. Nice catch :)