[Drone 0.5] Use branch exclusion rule to avoid running tests on CI for documentation changes

[shuklanirdesh82]

Avoid running tests on CI for documentation change using branch exclusion rule [depends on drone 0.5 release]

Currently CI is running for documentation change (e.g. README.md, CONTRIBUTING.md etc) even though there is no code change.

CI should not be invoked when there is a doc change.

/cc @tusharnt

[shuklanirdesh82]

Avoiding CI run can be achieved in two ways.

• Adding [SKIP CI] or [CI SKIP] at PR title i.e. first commit message while generating PR (#[SKIP CI] Adding information for skipping CI (#1141) and restarting CI run (#1107) #1213)
• Adding branch exclude rule to out out running CI job ( PR [WIP] Adding branch exclude rule to opt out running CI job #1171 is blocked due to Deploy drone 0.5 nodes  vmware/vic#4267) See [WIP] Adding branch exclude rule to opt out running CI job #1171 (comment) for more information.

[shuklanirdesh82]

let's stick with simpler approach that means "Adding [SKIP CI] or [CI SKIP] at PR title i.e. first commit message while generating PR (##1213)"

required work is done, closing this issue as wontfix; please feel free to reopen with some details about the reason for not using simpler approach.