should add extension path variables dynamically

[hoatle]

so that extension configs should have the right path, for example, chef cookbooks_path for https://github.com/teracyhq-incubator/teracy-dev-v05-compat/pull/2/files

We should have <extension-name>-path variable so that, only enabled extensions will have the associated <extension-name>-path, the path should not include slash character (/) at the end.

      cookbooks_path:
        - teracy-dev-v05-compat/vendor-cookbooks
        - teracy-dev-v05-compat/main-cookbooks

should become:

      cookbooks_path:
        - "%{teracy-dev-v05-compat-path}/vendor-cookbooks"
        - "%{teracy-dev-v05-compat-path}/main-cookbooks"

By supporting this, https://github.com/teracyhq-incubator/teracy-dev-v05-compat/pull/2 will not have to create a new configurator but using yaml config only.

[hoatle]

assigned to @phuonglm to handle this for the related PR.

[hoatle]

you can create: processors/extension_path.rb to work on this and register this processor before the variables.rb processor then it should work.

[hoatle]

settings['variables'] should be updated to include these dynamic vars

[hoatle]

related: https://github.com/teracyhq/dev/issues/497

If the above improvement is done, we can implement the feature of this issue on any extensions instead of waiting for teracy-dev-core.

[hoatle]

this should be done quickly, I guess it should not take more than 2 hours.

[hoatle]

extension_path = File.join(extension['path']['lookup'] || TeracyDev::DEFAULT_EXTENSION_LOOKUP_PATH,  extension['path']['extension'])

You can use Util.extension_lookup_path if suitable for the lookup_path

[hoatle]

this can be postponed, we don't have to rush for this, so assigned to @hieptranquoc for the next sprint instead.

[hoatle]

this cannot be postponed, required for https://github.com/teracyhq-incubator/teracy-dev-v05-compat/issues/1