Bundle state inconsistency in case of update failure

[PengZheng]

When entering celix_framework_bundleEntry_refreshBundleEntry, bundle is in resolved state. If any of the steps in celix_framework_bundleEntry_refreshBundleEntry fails, bundle state should be updated accordingly. Currently this is not the case.

Note that to fix this issue, #557 should also be considered. The ultimate goal is to fully support bundle update, and thus the following warning should be eliminated:

    fw_log(fw->logger, CELIX_LOG_LEVEL_WARNING, "Update bundle is not yet fully supported. Use at your own risk.");

[PengZheng]

Once #556 is resolved, the current implementation of uninstall can be renamed to "unload". Then update can be implemented as unload followed by install. This way, a refresh bundle is loaded from storage without any state inconsistency issues.

Additional benefits include:

• No need of bundleArchive_revise.
• Archive is read-only, thus thread-safety issues (e.g #526) go away.
• String copy in celix_bundleArchive_getLocation is unnecessary.
• Lots of redundancies can be eliminated. For example, each bundle will only have one module and one revision.