fix: not show unwanted warning

[jLopezbarb]

Proposed changes

While doing the release manual testing we discovered that there was an unwanted warning caused by #4254

Given the current implementation the only way to not show that warning was to calculate if the file was a Dockerfile before checking if it was an okteto manifest or a compose/stack file.

How to validate

1. Run okteto build -f Dockerfile on a file that is a valid Dockerfile and check that the warning is not shown

CLI Quality Reminders 🔧

For both authors and reviewers:

• Scrutinize for potential regressions
• Ensure key automated tests are in place
• Build the CLI and test using the validation steps
• Assess Developer Experience impact (log messages, performances, etc)
• If too broad, consider breaking into smaller PRs
• Adhere to our code style and code review guidelines

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 43.37%. Comparing base (535fdf3) to head (a5be81c).

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #4282   +/-   ##
=======================================
  Coverage   43.37%   43.37%           
=======================================
  Files         368      368           
  Lines       30012    30015    +3     
=======================================
+ Hits        13017    13020    +3     
  Misses      15876    15876           
  Partials     1119     1119