Add possibility to configure custom workflows directly within pom.xml

[pfink]

It would be nice to have a possibility to configure custom workflows directly within pom.xml without having the need of extra files. Use case: E.g. make a corporate super POMs that inherit custom workflows to child projects (would increase reusability).

Idea / Example (here in conjunction with the unleash plugin):

                [..]
                <plugin>
                  <groupId>com.itemis.maven.plugins</groupId>
                  <artifactId>unleash-maven-plugin</artifactId>
                  <version>2.6.0</version>
                  <dependencies>
                    <dependency>
                      <groupId>com.itemis.maven.plugins</groupId>
                      <artifactId>unleash-scm-provider-git</artifactId>
                      <version>2.1.0</version>
                    </dependency>
                  </dependencies>
                  <configuration>
                    <workflows>
                      <workflow>
                        <name>my-first-workflow</name>
                        <steps>
                          <tryfinally>
                            <try>
                              <step>firstStep</step>
                              <step>secondStep</step>
                            </try>
                            <finally>
                              <parallel>
                                <step>thirdStep</step>
                                <step>fourthStep</step>
                              </parallel>
                              <step>lastStep</step>
                            </finally>                            
                          </tryfinally>                        
                        </steps>
                      </workflow>
                      <workflow>
                        <name>my-second-workflow</name>
                        [..]
                      </workflow>
                    </workflows>          
                  </configuration>                  
                </plugin>
                [..]