Symbolic link support as a form of inheritance

### Your checklist for this issue

🚨 Please review the [guidelines for contributing](../blob/master/docs/CONTRIBUTING.md) to this repository.

- [x ] Link to any upstream changes that might be required (for example Jenkins Core pull request)

### Feature Request

A poor mans inheritance can be implemented using symbolic links for folders.

Given the following file structure

```
{config home}
│ base_configuration.yaml
└───animal
│ │ animal_config.yaml
└───dog
│ │ {symbolic link to animal}
│ │ dog_config.yaml
└───cat
│ │ {symbolic link to animal}
│ │ cat_config.yaml
```

It is possible to have configuration that is shared by "cat" and "dog" form part of animal configuration. adding any additional configuration files in the animal structure means that both dog and cat inherit these changes without having to manipulate new symbolically linked files.