Bump springboot from 2.7.9 to 2.7.11

[shoothzj]

Brief changelog

Bump springboot from 2.7.9 to 2.7.11.

Follow this checklist to help us incorporate your contribution quickly and easily:

• Read the Contributing Guide before making this pull request.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Write necessary unit tests to verify the code.
• Run mvn clean test to make sure this pull request doesn't break anything.
• Update the CHANGES log.

[codecov]

Codecov Report

Merging #4828 (c5a00e5) into master (8a7a149) will decrease coverage by 0.13%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #4828      +/-   ##
============================================
- Coverage     48.48%   48.36%   -0.13%     
+ Complexity     1726     1722       -4     
============================================
  Files           346      346              
  Lines         10827    10827              
  Branches       1078     1078              
============================================
- Hits           5250     5237      -13     
- Misses         5255     5268      +13     
  Partials        322      322              

see 2 files with indirect coverage changes

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[nobodyiam]

It looks like the snakeyml version referenced in 2.7.10 is still 1.30.

[shoothzj]

@nobodyiam My apologizes, I will wait for next springboot release.

[nobodyiam]

review again

[nobodyiam]

Hello, I am a serverless review bot on flows.network. Here are my reviews of code commits in this PR.

---

Commit 1

The patch is about upgrading the version of Spring Boot from 2.7.9 to 2.7.10. There are no potential problems identified in this patch, and it appears to be a straightforward update.

[shoothzj]

@nobodyiam @Anilople Although this springboot version doesn't bump snakeyaml's version. But I think it's also worth to update it because it also solve other cves. Like CVE-2023-20863 etc.

[nobodyiam]

LGTM