fix: skip volume mount translation into okteto manifest build

[jLopezbarb]

Proposed changes

If you try to run okteto build on a compose file that only have volume mounts We try to build the services but given that we've removed the build support for the volume mounts, we are not building anything which results into a weird case where the user get that it's going to build if it's not a git repo or no other output:

The correct behaviour must be to fallback to the v1 given that we don't have any service to build.

How to validate

1. Create the following docker-compose.yml:

version: '2'
services:
  postgres:
    image: bitnami/postgresql:11.14.0-debian-10-r28
    environment:
      POSTGRES_USER: test
      POSTGRES_PASSWORD: test
      POSTGRES_DB: test
    volumes:
      - ./schema.sql:/test/schema.sql

2. Run okteto build
3. Check that it's fullbacking to the build v1

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

[ifbyol]

Some CI job has failed but I think it is some transient error with an external service. It looks good!

[codecov]

Codecov Report

Merging #4231 (53f6ce3) into master (d2065c3) will increase coverage by 0.01%.
Report is 1 commits behind head on master.
The diff coverage is 33.33%.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #4231      +/-   ##
==========================================
+ Coverage   45.66%   45.68%   +0.01%     
==========================================
  Files         303      303              
  Lines       27539    27527      -12     
==========================================
- Hits        12577    12575       -2     
+ Misses      13889    13879      -10     
  Partials     1073     1073