Add Eclipse project files for submodules and update README

- Add .classpath and .project for app submodule
- Add .project for cicsbundle submodule
- Update buildship settings
- Remove outdated IDE refresh note from README
- Ensures clean Eclipse import without manual refresh

Author: IvanHargreaves

README.md

@@ -155,11 +155,8 @@ mvnw.cmd clean verify
    - Right-click on root project → Run As → Gradle Build (or Maven Build)
    - Goals: `clean build` (Gradle) or `clean verify` (Maven)
 
-**Notes:**
+**Note:**
 - When building a WAR file for deployment to Liberty it is good practice to exclude Tomcat from the final runtime artifact. We demonstrate this in the pom.xml with the *provided* scope, and in build.gradle with the *providedRuntime()* dependency.
-- If you import the project to your IDE, you might experience local project compile errors. To resolve these errors you should run a tooling refresh on that project. For example, in Eclipse: right-click on "Project", select "Gradle -> Refresh Gradle Project", **or** right-click on "Project", select "Maven -> Update Project...".
-
->Tip: *In Eclipse, Gradle (buildship) is able to fully refresh and resolve the local classpath even if the project was previously updated by Maven. However, Maven (m2e) does not currently reciprocate that capability. If you previously refreshed the project with Gradle, you'll need to manually remove the 'Project Dependencies' entry on the Java build-path of your Project Properties to avoid duplication errors when performing a Maven Project Update.*
 
 ---