endpoint: Don't set compilationExecuted on Reload
endpoint: Don't set compilationExecuted on Reload

When performing a simple reload of the datapath logic, don't set
`compilationExecuted`, as that setting is used to govern whether the
endpoint state directories get swapped from the `xxx_next` directory to
the `xxx` directory. Since ReloadDatapath() doesn't populate the object
file in the `xxx_next` directory, this leads to a situation where no
pre-compiled datapath object file is available, and if another
subsequent DatapathReload occurs after this, it fails and puts the
endpoint into the `not-ready` state.

Signed-off-by: Joe Stringer <16a9a54ddf4259952e3c118c763138e83693d7fd@covalent.io>

tklauser/cilium,michi-covalent/cilium,scanf/cilium,scanf/cilium,cilium-team/cilium,scanf/cilium,scanf/cilium,tklauser/cilium,tgraf/cilium,cilium/cilium,cilium/cilium,tklauser/cilium,michi-covalent/cilium,cilium/cilium,michi-covalent/cilium,michi-covalent/cilium,scanf/cilium,scanf/cilium,tgraf/cilium,tgraf/cilium,tgraf/cilium,scanf/cilium,tklauser/cilium,michi-covalent/cilium,cilium/cilium,cilium-team/cilium,tklauser/cilium,cilium/cilium,tgraf/cilium,tgraf/cilium