Soft dependency support for resources

[r3ps4J]

Goal of this PR

This PR adds support for soft dependencies, indicated by the manifest entries soft_dependency and soft_dependencies. Soft dependencies only get started if they exist, making it possible to add optional dependencies to a resource. This is useful when a resource can work fine without a dependency, but can benefit from having access to that dependency.

See the proposal on the forum for more details: https://forum.cfx.re/t/soft-dependencies-for-resources/5281288/1

How is this PR achieving the goal

This PR implements soft dependencies by loading them the same way as normal dependencies, but if one is missing or fails to start it skips it and continues to the next one. It also still prints the same information as with regular dependencies, and only tries to load the soft dependencies after the hard dependencies have been checked and loaded to prevent starting them when the resource can't start anyway.

This PR specifically adds the const bool soft = false parameter to the loadDeps function. The paramter has a default value of false, to remain backwards compatible. When soft is set to true the following things are different as opposed to loading hard dependencies:

• Constraints are not checked, as having optional constraints makes little sense.
• When a soft dependency is not found, the loop continues instead of returning false early to stop the resource from loading.
• The soft dependency does not get stored in resourceDependants, as stopping the soft dependency should not prevent the resource from running.
• When a soft dependency fails to start, the loop continues instead of returning false early to stop the resource from loading and storing the dependency in resourceDependencies to start it later.

This PR applies to the following area(s)

This applies to the server and clients. The changes were made in citizen-resources-core.

Successfully tested on

The changes were tested on the server and FiveM client.

Game builds: b3095

Platforms: Windows

Checklist

• Code compiles and has been tested successfully.
• Code explains itself well and/or is documented.
• My commit message explains what the changes do and what they are for.
• No extra compilation warnings are added by these changes.

Fixes issues

None.

[r3ps4J]

Okay I wanted to rename the branch on my repo, but github doesn't seem to like it.

[Nobelium-cfx]

Thank you for the contribution!

I understand the motivation behind this PR and the code looks reasonable. But I don't have enough context to make the final call on if it's actually needed. @prikolium-cfx WDYT?

[prikolium-cfx]

Thank you for the contribution!

I understand the motivation behind this PR and the code looks reasonable. But I don't have enough context to make the final call on if it's actually needed. @prikolium-cfx WDYT?

Should be discussed together with team. Can't say right now pros and cons of such decision

[r3ps4J]

Sounds good! I added some quotes around the resource names to clarify what is and what is not part of the resource names. This also makes it match the other traces in the dependency loader.

[r3ps4J]

@prikolium-cfx any updates on this?