I'm not sure why you would want to do that, as it seems unusual for any applications that I am aware of.
The fact is that he does want to do it, so let's do him the courtesy of assuming that he's got a good reason.
I'm not sure that you can do it directly. By and large you can do things like adding the target processor by putting e.g.
jds6600-$(TargetCPU)-$(TargetOS)-$(LCLWidgetType)
into "Target file name" noting that the support for this being used with "Set compiler options as default" is patchy.
If you look at the IDE's Tools -> Configure External Tools -> Add -> Macros you can see what's usable in that context, although I think there's additional subtleties in some of the naming.
You can also use the IDE's Compiler Commands -> Execute after -> Command to do various stuff, which suggests that if your target program had a --version option which output the build numbers, then you could filter that using a script and rename the binary.
An alternative would be to hold the build numbers in some sort of external file and inject them into the IDE's files (probably the .lpi) but if you attempted this you would be infringing on the developers' prerogatives by assuming that they would never change that file's format which would be extremely rash. For that same reason, I would suggest not attempting to have your final renaming operation not attempting to extract the build version from the IDE files itself.
See e.g.
https://github.com/MarkMLl/Mastech_ms2115b for an example of processing the --version option in a project's .lpr and extracting the build version from the executable.
MarkMLl