<!---
Thanks so much for your contribution! If this is your first time
contributing, please ensure that you have read the
[CONTRIBUTING](https://github.com/pulumi/pulumi/blob/master/CONTRIBUTING.md)
documentation.
-->
# Description
Add support for two new fields to a project template block:
* `DisplayName` which is used to store a user friendly template name
* `Tags` which is used to store additional template metadata that is
author-defined (e.g. team, environment, etc.)
This information will be used in the near-term within the console but
longer term could also be used within the CLI.
## Checklist
- [x] I have run `make tidy` to update any new dependencies
- [x] I have run `make lint` to verify my code passes the lint check
- [x] I have formatted my code using `gofumpt`
<!--- Please provide details if the checkbox below is to be left
unchecked. -->
- [ ] I have added tests that prove my fix is effective or that my
feature works
Since this change only adds optional fields I didn't think tests would
be worthwhile. I can add tests if it's thought they would be valuable.
<!---
User-facing changes require a CHANGELOG entry.
-->
- [x] I have run `make changelog` and committed the
`changelog/pending/<file>` documenting my change
<!--
If the change(s) in this PR is a modification of an existing call to the
Pulumi Cloud,
then the service should honor older versions of the CLI where this
change would not exist.
You must then bump the API version in
/pkg/backend/httpstate/client/api.go, as well as add
it to the service.
-->
- [ ] Yes, there are changes in this PR that warrants bumping the Pulumi
Cloud API version
<!-- @Pulumi employees: If yes, you must submit corresponding changes in
the service repo. -->
Also separate the validation and merging of project-to-stack values, to
allow us to apply in values even if they're secure and we don't have an
available decrypter. We can't validate that they're all correct, but it
means at least `config get` can do a best effort retrival for config
values.
We recently started validating the `Pulumi.yaml` file against its schema, leading to the following error when the `refresh: always` option is specified:
```
error: could not load current project: 1 error occurred:
* #/options/refresh: expected boolean, but got string
```
The problem is the feature is expecting a string value of `"always"` but the schema for the project file is incorrectly specified as `boolean`.
This change fixes the schema, which avoids the error. A separate change will fix the documentation at https://www.pulumi.com/docs/reference/pulumi-yaml/#options-options