Add more anchors in the properties appendix

[garyrussell]

Thanks for adding anchors to the appendix (#8237).

This is a big improvement, but I wonder if it could be a bit more granular; for example Integration Properties covers many technologies and properties.

It would be nice if we could jump directly to rabbitmq or kafka instead of having to scroll past all the other properties.

[snicoll]

I can see two ways we could fix this issue and both seems to lead to the creation of more tables. If we want to do this in a global fashion, perhaps our current description could have the notion of "sub-sections" so that we could do something like this:

.addSection("integration")
    .withSection("spring.activemq").withSection("spring.artemis").withSection("spring.batch") ...

That would create one sub-section under the current integration section with the same naming pattern (i.e. "spring.activemq properties") and a dedicated anchor.

If we don't want to go down that route, we could split things up a bit and just remove the high-level section and just listing the prefix one by one. In other words, remove the integration section and list only the prefixes. Doc output should help us decide what's best probably.

[garyrussell]

It is not just the Integration section; I see a similar problem in the Data section with hundreds of properties covering many technologies.

spring-guides/gs-messaging-redis#20 (comment)

[Buzzardo]

It would be good to be able to link directly to a property from other documents. You need not have a heading for each anchor. Inline anchors can go anywhere.

[wilkinsona]

I've started working on something for this that will make each individual property linkable.