Add first set of profile commands

[MatteoPologruto]

Please check if the PR fulfills these requirements

See how to contribute

• The PR has no duplicates (please search among the Pull Requests
  before creating one)
• The PR follows
  our contributing guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)
• UPGRADING.md has been updated with a migration guide (for breaking changes)
• configuration.schema.json updated if new parameters are added.

What kind of change does this PR introduce?

Code enhancement

What is the current behavior?

Operations on the sketch.yaml project file must be done manually.

What is the new behavior?

First set of profile commands:

1. profile init [<PATH>] [-m <PROFILE_NAME -b <FQBN>] [--default] creates a sketch.yaml file at the provided path. By default it creates the file in the current directory. A new profile can be added to the file by providing a profile name and FQBN (mandatory). The platform is detected automatically. If there is only one profile, it is automatically set as the default profile, otherwise the flag --default must be used. The command fails in the following cases:
   • the path does not exist or the main sketch file is missing
   • the FQBN is wrong or the platform related to it is not installed locally
2. profile lib add <LIB_NAME@LIB_VERSION> [-m <PROFILE_NAME] [--dest-dir <PATH>] adds a library to the provided profile or to the default one. By default it checks for the sketch.yaml file in the current directory.
3. profile lib remove <LIB_NAME> [-m <PROFILE_NAME] [--dest-dir <PATH>] removes a library from the provided profile or from the default one. By default it checks for the sketch.yaml file in the current directory.
4. profile set-default <PROFILE_NAME> [--dest-dir <PATH>] sets the default profile to an existing profile. By default it checks for the sketch.yaml file in the current directory.
5. profile dump [<PATH>] dumps the content of the sketch.yaml file. It supports the yaml and json formats.

Does this PR introduce a breaking change, and is titled accordingly?

Other information

[codecov]

Codecov Report

❌ Patch coverage is 66.25000% with 216 lines in your changes missing coverage. Please review.
✅ Project coverage is 68.29%. Comparing base (20e315c) to head (65354c4).

Files with missing lines	Patch %	Lines
commands/service_profile_lib_add.go	57.89%	30 Missing and 10 partials ⚠️
internal/cli/profile/dump.go	20.93%	33 Missing and 1 partial ⚠️
internal/arduino/sketch/profiles.go	52.94%	26 Missing and 6 partials ⚠️
commands/service_profile_lib_list.go	0.00%	20 Missing ⚠️
internal/cli/profile/lib.go	87.16%	16 Missing and 3 partials ⚠️
commands/service_profile_dump.go	0.00%	16 Missing ⚠️
commands/service_profile_lib_remove.go	54.54%	10 Missing and 5 partials ⚠️
commands/service_profile_init.go	77.96%	9 Missing and 4 partials ⚠️
commands/service_profile_set_default.go	52.63%	6 Missing and 3 partials ⚠️
commands/service_library_install.go	50.00%	5 Missing and 2 partials ⚠️
... and 3 more

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2917      +/-   ##
==========================================
- Coverage   68.36%   68.29%   -0.08%     
==========================================
  Files         241      252      +11     
  Lines       22731    23328     +597     
==========================================
+ Hits        15541    15932     +391     
- Misses       5992     6166     +174     
- Partials     1198     1230      +32     

Flag	Coverage Δ
unit	68.29% <66.25%> (-0.08%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[kittaakos]

Hello, this is great 🔥 Maybe you want to consider adding and removing multiple libs (later cores) with a single request. I do not know how it performs, but when a user interface wants to initialize a profile from a set of libraries and cores, one request would be better than multiple ones.

---

Update: I checked the changes only from the point of the proto API as a client.

[alessio-perugini]

Great job! 🚀

We have a bug in the long standing:

arduino-cli/internal/arduino/sketch/profiles.go

Lines 166 to 167 in 55f86b5

	res += p.Platforms.AsYaml()
	res += p.Libraries.AsYaml()

arduino-cli profile init --profile Uno_profile -b arduino:avr:uno /tmp/sk

cat /tmp/sk/sketch.yaml

profiles:
  Uno_profile:
    fqbn: arduino:avr:uno
    platforms:
      - platform: arduino:avr (1.8.6)
    libraries:

default_profile: c

You can see here that it produces libraries: without [], this is an invalid yaml.

Basically we have to check if the items == 0, then we either skip that property or we set libraries: [].
I'm afraid it could also happen for the platforms so I'd put that check there too.

[alessio-perugini]

Do we have some kind of internal API that we can use to retrieve platform <-> index URL?

[alessio-perugini]

cc: @cmaglie

[per1234]

I feel that the design of the profile dump command is inappropriate. This command is actually printing the data of the entire sketch project file, not the build profile data alone. Although the primary usage of the sketch project file is currently for defining build profiles, it is not limited to this purpose and there is a good chance that it will be used for additional things unrelated to build profiles as time goes on.

The profile dump command should be a tool for printing the data from a build profile.

If you want a tool for printing the sketch project file, that should go somewhere else, such as under the sketch command (e.g., sketch project dump), not under the profile command.

If the user doesn't specify a profile ID, it should print the default build profile from the sketch project file. An --all flag could be added to cause it to print all build profiles present in the sketch project file.