Rename organisation to camel-tooling

So the organization can host tooling for other IDEs such as Eclipse, Che, and others. And also tooling that may not be tied to an IDE editor.

We can then have some more common modules that the different tools can reuse, as there is a bunch of logic in the existing camel-idea-plugin that is not directly coupled to the IDEA API but would benefit being neutral and reusable by other tools.

Currently how the camel-idea-plugin is built and released is that its just a .zip file that has everything that gets updated at a jetbrains website.

If we need to release JAR files to maven central, then we need to use maven coordinate that is not org.apache as they are the ASF organization. And therefore we need to use org.cameltooling or something like that. But that is a discussion to take when we get to that bridge.

Notice that its only the organization that will be renamed. Each sub-project in this organization will have its own git repo, eg the camel-idea-plugin git repo will stay as-is.

[davsclaus]

Okay I think we should rename this organization in the weekend - that gives a little time for @fharms and @bennetelli to catch up.

Here is what github says about a rename with what happens automatic and what not. https://help.github.com/articles/renaming-an-organization/

So what if we do

1. Rename the organization to camel-tooling on saturday
2. Update the organization logo to the one that @lhein posted above
3. Refactor the source code to use com.github.cameltooling as base package name.

Any comments

[lhein]