fix: panics on command initialsation

[jLopezbarb]

Signed-off-by: Javier Lopez javier@okteto.com

Proposed changes

Fixes DEV-378

We have detected several panics that have been fixed on this PR. Summarising them in bullet points:

1. okteto up:
   1.1 Fixes a panic when okteto up is executed on a manifest without dev section
   1.2 Fixes a panic when okteto up is executed on a folder without manifest and infering it
2. okteto init
   2.1 Fixes a panic when okteto init has to deploy (need to click on yes)
   2.2 Fixes a panic when okteto init is set with k8sLogger

How to validate

Check that the scenarios described above are working without a panic

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

Attention: Patch coverage is 5.55556% with 17 lines in your changes are missing coverage. Please review.

Project coverage is 43.05%. Comparing base (9837398) to head (ae908d5).
Report is 2 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #4322   +/-   ##
=======================================
  Coverage   43.05%   43.05%           
=======================================
  Files         371      371           
  Lines       30048    30060   +12     
=======================================
+ Hits        12936    12942    +6     
- Misses      15978    15986    +8     
+ Partials     1134     1132    -2     

[github-actions]

The backport to release-2.26 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-release-2.26 release-2.26
# Navigate to the new working tree
cd .worktrees/backport-release-2.26
# Create a new branch
git switch --create backport-4322-to-release-2.26
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 ad8c37c3002a2b123134af95fd865b94b1101c0d
# Push it to GitHub
git push --set-upstream origin backport-4322-to-release-2.26
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-release-2.26

Then, create a pull request where the base branch is release-2.26 and the compare/head branch is backport-4322-to-release-2.26.