Create rules for dropped servlet-based integrations

According to the [migration guide](https://github.com/spring-projects/spring-framework/wiki/Upgrading-to-Spring-Framework-6.x#web-applications-2):

> Several outdated Servlet-based integrations have been dropped: e.g. Apache Commons FileUpload (org.springframework.web.multipart.commons.CommonsMultipartResolver), and Apache Tiles as well as FreeMarker JSP support in the corresponding org.springframework.web.servlet.view subpackages. We recommend org.springframework.web.multipart.support.StandardServletMultipartResolver for multipart file uploads and regular FreeMarker template views if needed, and a general focus on REST-oriented web architectures.

Investigate and create rules if necessary.

In the rule description and message, try to be as verbose and clear as possible. Code examples are always welcome and useful. Feel free to use markdown syntax for these.

Start with the linked Spring Framework 6.x migration guide and review the existing rules in this repository to identify how dropped Servlet-based integrations are represented. Add rules where necessary for the listed integrations, with verbose descriptions, messages, and useful markdown code examples; done means the relevant dropped integrations are covered clearly.

Written by the indexing model from the issue text.