WARP stale function GUIDs when view modified

Currently we cache the function GUIDs indefinitely and do not regenerate them when we:

1. Rebase the binary
2. Add sections / segments

Both happen most frequently in the context of firmware binaries. Once these occur we should regenerate guids in the background, since the guids can be altered.