Feature/23 feature request pin file loading

[Lypsolon]

TODO

• Make sure that ayon-cpp-dev-tools will be included as a cmake project, not via the CMakeInclude.txt

  • include("${CMAKE_CURRENT_SOURCE_DIR}/ext/ayon-cpp-dev-tools/CMakeInclude.txt")

• fully clean build script

• write Documentation for pinning file loading (Technical)

• Write refactoring Proposal (proposal should remove the extra loop in _Rresolve() func)

• check if bool m_staticParentCache; is used in resolver.h if not, remove

• change getCachePtr() back to the old return behavior

• move pinning file helper to its own file set

• rewrite readme.md

• re-implement the sdf strip macro

• activate SDF Strip macro for the selected dccs (activated for all Build Plugins for now )

• allow for root replace on both key and value portion of the pinning file.

Changelog Description

Additional info

Testing notes:

1. start with this step
2. follow this step

[Lypsolon]

@dee-ynput and @BigRoy, I requested you because of the documentation part mainly. just FYI

[robin-ynput]

Hey @Lypsolon, overall that looks good to me.
The cpp part reads fine, I had no trouble understanding your logic here.

One recommendation for the future, this could easily have been 3 separated PRs (easier to review):

• new cache logic feature implementation with dependencies update
• rework build script in Python
• documentation

[Lypsolon]

@BigRoy, @dee-ynput and @antirotor.
im currently thinking about how we deal with the SDF args situation.
we have the option to enable and disable the removeSdfArgs function per build plugin.

but i have no idea what library's and tools have the SdfArgs problem so im asking myself should we
A: disable it for everything right now and then see where it errors when users get there hands to it ?
B: test by hand what application has the problem
C: enable it for everything and disable it when we do some more testing ? (in the CI Epic we might be able to add some tests for this ?)

[EDIT]: for now we just enable the SDF ARGS remove function for all BuildPlugins we can deactivate the macro per BuildPlugin when we find out who needs it and who dosnt.
its a performance penalty and i dont like it but the Ayon-Server is also a Performance penalty.