Redmine#6189: Store the hardcoded bootstrap file in a variable instead o...

...f using it directly to prevent old GCCs from failing due to fprintf usage as a macro

Ticket: https://dev.cfengine.com/issues/6189
I remember back when I was working with Symbian, whether you used const or not decided whether the ARM compiler would put your data in the read only section or the data section. The read only section was shared between processes and in a true read only memory page, so you could not modify it. Since we were making a library, it also meant that whether or not you used const made a significant difference to memory usage: If it were const, it would not only be shared, but could even be discarded from memory entirely, since you knew that you could get the same data back from the flash storage at any time. Not making it const, however, meant that everyone using the library would have a copy that needed to remain in memory.

Whether it applies to desktop Linux, I don't know though. :-)