ebs-warmup: added exec mode for warmup-steps.sh

[YuJuncen]

What problem does this PR solve?

The current warmup_steps.sh isn't executable in the ebs-warmup container, which forces the caller to change the permission firstly for it.

What is changed and how does it work?

This added execution permission for the entry script.

Code changes

• Has Go code change
• Has CI related scripts change

Tests

• Unit test
• E2E test
• Manual test

- [ ] No code

Release Notes

Please refer to Release Notes Language Style Guide before writing the release note.

NONE

[codecov-commenter]

Codecov Report

Merging #5258 (24e67fa) into master (cb6b246) will increase coverage by 0.00%.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #5258   +/-   ##
=======================================
  Coverage   57.26%   57.26%           
=======================================
  Files         246      246           
  Lines       29806    29806           
=======================================
+ Hits        17067    17069    +2     
+ Misses      11078    11077    -1     
+ Partials     1661     1660    -1     

Flag	Coverage Δ
unittest	57.26% <ø> (+<0.01%)	⬆️

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BornChanger, WangLe1321

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [BornChanger,WangLe1321]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[BornChanger]

/retest

[BornChanger]

/cherry-pick release-1.5

[ti-chi-bot]

@BornChanger: once the present PR merges, I will cherry-pick it on top of release-1.5 in the new PR and assign it to you.

In response to this:

/cherry-pick release-1.5

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[ti-chi-bot]

@BornChanger: The label(s) /release-1.5 cannot be applied, because the repository doesn't have them.

In response to this:

/cherry-pick release-1.5

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[BornChanger]

/retest

[ti-chi-bot]

@YuJuncen: Your PR was out of date, I have automatically updated it for you.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2023-08-21 06:06:04.732050865 +0000 UTC m=+1129529.281066854: ☑️ agreed by BornChanger.
• 2023-08-22 08:15:21.291937875 +0000 UTC m=+1223685.840953861: ✖️🔁 reset by ti-chi-bot[bot].

[ti-chi-bot]

New changes are detected. LGTM label has been removed.

[ti-chi-bot]

@BornChanger: new pull request created to branch release-1.5: #5261.

In response to this:

/cherry-pick release-1.5

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.