Remove support for `IPageLayout.addFastView`

[ptziegler]

This method has been removed with eclipse-platform/eclipse.platform.ui#3606 and its absence is causing test failures such as https://github.com/eclipse-windowbuilder/windowbuilder/runs/59499671442:

!ENTRY org.eclipse.wb.core 4 4 2026-01-05 18:26:24.238
!MESSAGE Designer [1.23.0.202601051745.202601051755]: 502 (Unable to load *.wbp-component.xml description.). org.eclipse.ui.IPageLayout
!STACK 0
org.eclipse.wb.internal.core.utils.exception.DesignerException: 502 (Unable to load *.wbp-component.xml description.). org.eclipse.ui.IPageLayout
	at org.eclipse.wb.internal.core.model.description.helpers.ComponentDescriptionHelper.getDescription0(ComponentDescriptionHelper.java:422)
	at org.eclipse.wb.internal.core.model.description.helpers.ComponentDescriptionHelper.getDescription0(ComponentDescriptionHelper.java:290)
	at org.eclipse.wb.internal.core.model.description.helpers.ComponentDescriptionHelper.getDescription(ComponentDescriptionHelper.java:259)
	at org.eclipse.wb.internal.core.model.JavaInfoUtils.createJavaInfo(JavaInfoUtils.java:392)
	at org.eclipse.wb.internal.rcp.parser.ParseFactory.getRootContext(ParseFactory.java:157)
	at org.eclipse.wb.internal.core.parser.JavaInfoParser.prepareParseContext(JavaInfoParser.java:1183)
	at org.eclipse.wb.internal.core.parser.JavaInfoParser.parse(JavaInfoParser.java:242)
	at org.eclipse.wb.internal.core.parser.JavaInfoParser.lambda$0(JavaInfoParser.java:150)
	at org.eclipse.wb.internal.core.utils.execution.ExecutionUtils.runDesignTime(ExecutionUtils.java:159)
	at org.eclipse.wb.internal.core.parser.JavaInfoParser.parse(JavaInfoParser.java:150)
	at org.eclipse.wb.internal.core.editor.DesignPage.internal_refreshGEF(DesignPage.java:554)
	at org.eclipse.wb.internal.core.editor.DesignPage$8$1.run(DesignPage.java:469)
[...]
Caused by: org.eclipse.wb.internal.core.utils.check.AssertionFailedException: No such method org.eclipse.ui.IPageLayout.addFastView(java.lang.String) during parsing org.eclipse.ui.IPageLayout
	at org.eclipse.wb.internal.core.utils.check.Assert.fail(Assert.java:227)
	at org.eclipse.wb.internal.core.utils.check.Assert.isNotNull2(Assert.java:211)
	at org.eclipse.wb.internal.core.model.description.helpers.ComponentDescriptionHelper.process(ComponentDescriptionHelper.java:590)
	at org.eclipse.wb.internal.core.model.description.helpers.ComponentDescriptionHelper.getDescription0(ComponentDescriptionHelper.java:377)
	... 219 more

[ptziegler]

WindowBuilder supports multiple versions of the IPageLayout.wbp-component.xml. This version is calculated from SWT.getVersion().

The problem: We only look at the first digit of the minor version, which means that 4972 (the SWT version corresponding to the 2026-03 release and also where this incompatibility occurs) gets mapped to the version 4.9. But this is also the case for the 2025-12 release. In other words: WindowBuilder can't distinguish between the 2026-03 and the 2025-12.

WindowBuilder is also searching for an exact match. So if I were to include the other digits, I would now have to create a IPageLayout.wbp-component.xml file for the 4972, 4973, ...

I don't think it makes sense to keep using the SWT version. Instead I'll bump the minor version to 10 and increase it, whenever there is a "breaking" change on the SWT/Platform side.