Profiling images can now be generated from crossbuild images

[marc-casavant]

Key Changes:

• Profiling images are built FROM <CROSSBULD_IMAGE>
• Profiling images install useful profiling tools
• Profiling images do not build FreeRADIUS

Build Steps Example:

Generate the crossbuild Dockerfile.cb:
make crossbuild.ubuntu24.regen

Build the crossbuild base image:
make crossbuild.ubuntu24.build

Generate the profiling Dockerfile.prof:
make crossbuild.ubuntu24.profile.regen

Build the profiling image:
make crossbuild.ubuntu24.profile.build

[mcnewton]

few things to look at

[mcnewton]

Not entirely convinced these should be in the help. They should be used by the CI jobs only, it's not helpful to have extra targets for developers that they should never use.

[alandekok]

As a minor point, help is useful. :) Especially if I want to run profiling tools locally.

As seen here, it's a bit of a pain to get the profiling builds up and running. It's a lot easier to do make profiling

So I'm OK with leaving this in.

[mcnewton]

Agreed on the ones that developers use. But some of these targets are really only for CI, which might be confusing if a developer tries to use them. They're the ones I suggest not adding to help :)

As long as it's clear, then np.

[alandekok]

If the targets are only for CI, then there's no need to print them out in the help text.

[marc-casavant]

I kinda like having those in the help text :) Helps my brain, but I'm okay to remove the extra info in the help text is that's what we prefer.

[marc-casavant]

I believe the targets are useful for developers, especially when used with profiling multi-server tests.