Ensure none of our configuration files are executable

What does this MR do?

I use the following section in my git pre-push hook:

if [[ -x ./scripts/lint-doc.sh ]]; then
  if git changes-in origin/master.. | grep ".*.md"; then
    ./scripts/lint-doc.sh
  else
    echo 'No documentation changes'
  fi
fi

i.e. I lint the docs if there are any docs to lint.

This has worked well for some time until for some reason one of our files started running afoul of the executable bit check. This MR fixes that small matter.

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

No new tests required.