added new tomcat and jenkins profiles using official tomcat module

While tomcat version 7.0.25 of tomcat is used here, it does not seem to be able to properly handle the way the tomcat module refreshes the tomcat service and reloads the new Jenkins version. I think we should bump up to 7.0.57 which is the current latest version which handles this properly. This also requires replacing the current tomcat module in the environment with the official one from the Puppet Forge.
We should use `include profile::tomcat` instead class declaration.

Declaring classes (using resource-like syntax to instantiate and pass parameters to a class) is not idempotent, which means that if we do it here in an application profile, we cannot compose any additional application profiles onto a single system. Effectively, this pattern would render `profile::app::jenkins` incompatible with `profile::app::plsample`, or other hypothetical apps. 

Not using class declaration means we can't customize the `profile::tomcat` class as part of adding `profile::app::jenkins` to a system, but I think that's ok.

There are a lot of tradeoffs and considerations here but for the demo environment we should strive for ease of understanding. `profile::app::jenkins` can either stand up a dedicated tomcat instance for itself, or make use of a common instance defined in `profile::tomcat`. We should implement the latter.

There's a general note on class declaration in https://docs.puppetlabs.com/guides/style_guide.html#general-philosophies which I actually disagree with in part, but I'm referencing it as a good indicator of the consternation class declaration vs. include can cause.

tl;dr: please modify the `profile::app::jenkins` class to `include profile::tomcat`. Similarly, we should either `include java` or create a `profile::java` class that can be included.